Skip to content

Incorrect Authorization in Apache Solr

Critical severity GitHub Reviewed Published Feb 10, 2022 to the GitHub Advisory Database • Updated Mar 17, 2025

Package

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

Affected versions

>= 6.6.0, < 8.6.3

Patched versions

8.6.3
maven org.apache.solr:solr-parent (Maven)
>= 6.6.0, < 8.6.3
8.6.3
maven org.apache.solr:solr-solrj (Maven)
>= 6.6.0, < 8.6.3
8.6.3

Description

Apache Solr versions 6.6.0 to 6.6.6, 7.0.0 to 7.7.3 and 8.0.0 to 8.6.2 prevents some features considered dangerous (which could be used for remote code execution) to be configured in a ConfigSet that's uploaded via API without authentication/authorization. The checks in place to prevent such features can be circumvented by using a combination of UPLOAD/CREATE actions. This issue is patched in 8.6.3.

References

Published by the National Vulnerability Database Oct 13, 2020
Reviewed Apr 14, 2021
Published to the GitHub Advisory Database Feb 10, 2022
Last updated Mar 17, 2025

Severity

Critical

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
Low
Privileges required
None
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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(99th percentile)

Weaknesses

CVE ID

CVE-2020-13957

GHSA ID

GHSA-3c7p-vv5r-cmr5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.