Skip to content

Apache Solr Kerberos delegation token functionality flaws

High severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Jan 29, 2023

Package

maven org.apache.solr:solr-core (Maven)

Affected versions

>= 6.2.0, < 6.6.1

Patched versions

6.6.1

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.

References

Published by the National Vulnerability Database Sep 18, 2017
Published to the GitHub Advisory Database May 14, 2022
Reviewed Nov 8, 2022
Last updated Jan 29, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.059%
(26th percentile)

Weaknesses

CVE ID

CVE-2017-9803

GHSA ID

GHSA-f553-j2gv-g5r9

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.