Skip to content

GHSA-f553-j2gv-g5r9 CVE-2017-9803

Apache Solr Kerberos delegation token functionality flaws

High Maven
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
2.19%
Chance of exploitation in the next 30 days. Higher than 82.47% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
Fix
6.6.1
Upgrade org.apache.solr:solr-core to this version or later

Description

Apache Solr's Kerberos plugin can be configured to use delegation tokens, which allows an application to reuse the authentication of an end-user or another application. There are two issues with this functionality (when using SecurityAwareZkACLProvider type of ACL provider e.g. SaslZkACLProvider). Firstly, access to the security configuration can be leaked to users other than the solr super user. Secondly, malicious users can exploit this leaked configuration for privilege escalation to further expose/modify private data and/or disrupt operations in the Solr cluster. The vulnerability is fixed from Apache Solr 6.6.1 onwards.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.solr:solr-core
>= 6.2.0, < 6.6.1
6.6.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.solr:solr-core Maven → 6.6.1

maven
<dependency><groupId>org.apache.solr</groupId><artifactId>solr-core</artifactId><version>6.6.1</version></dependency>
gradle
implementation("org.apache.solr:solr-core:6.6.1")

Severity breakdown

CVSS 3.0 7.5

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2019-17558
Improper Input Validation in Apache Solr
High Known exploited Also affects org.apache.solr:solr-core
CVE-2019-0193
XML External Entity (XXE) Injection in Apache Solr
High Known exploited Also affects org.apache.solr:solr-core
GHSA-qhr7-h655-pw6r
Apache Solr has hardcoded credentials in the Basic Authentication setup tool
Critical Also affects org.apache.solr:solr-core
GHSA-vc2w-4v3p-2mqw
Apache Solr: Insufficient file-access checking in standalone core-creation requests
High Also affects org.apache.solr:solr-core
GHSA-qr3p-2xj2-q7hq
Apache Solr: Unauthorized bypass of certain "predefined permission" rules in the RuleBasedAuthorizationPlugin
High Also affects org.apache.solr:solr-core
GHSA-68r2-fwcg-qpm8
Apache Solr vulnerable to Execution with Unnecessary Privileges
Medium Also affects org.apache.solr:solr-core
GHSA-4p5m-gvpf-f3x5
Apache Solr Relative Path Traversal vulnerability
Medium Also affects org.apache.solr:solr-core
GHSA-37vr-vmg4-jwpw
Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets
High Also affects org.apache.solr:solr-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor