Skip to content

Server-Side Request Forgery in Apache Solr

High severity GitHub Reviewed Published May 10, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

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

Affected versions

< 8.8.2

Patched versions

8.8.2

Description

The ReplicationHandler (normally registered at "/replication" under a Solr core) in Apache Solr has a "masterUrl" (also "leaderUrl" alias) parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. To prevent a SSRF vulnerability, Solr ought to check these parameters against a similar configuration it uses for the "shards" parameter. Prior to this bug getting fixed, it did not. This problem affects essentially all Solr versions prior to it getting fixed in 8.8.2.

References

Published by the National Vulnerability Database Apr 13, 2021
Reviewed Apr 14, 2021
Published to the GitHub Advisory Database May 10, 2021
Last updated Feb 1, 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
Changed
Confidentiality
High
Integrity
Low
Availability
None

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:H/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS score

95.103%
(99th percentile)

Weaknesses

CVE ID

CVE-2021-27905

GHSA ID

GHSA-5phw-3jrp-3vj8

Source code

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