Skip to content

Apache Solr insecure inter-node communication

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

>= 5.3.0, < 5.5.5
>= 6.0.0, < 6.6.0

Patched versions

5.5.5
6.6.0

Description

Apache Solr uses a PKI based mechanism to secure inter-node communication when security is enabled. It is possible to create a specially crafted node name that does not exist as part of the cluster and point it to a malicious node. This can trick the nodes in cluster to believe that the malicious node is a member of the cluster. So, if Solr users have enabled BasicAuth authentication mechanism using the BasicAuthPlugin or if the user has implemented a custom Authentication plugin, which does not implement either "HttpClientInterceptorPlugin" or "HttpClientBuilderPlugin", his/her servers are vulnerable to this attack. Users who only use SSL without basic authentication or those who use Kerberos are not affected.

References

Published by the National Vulnerability Database Jul 7, 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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.283%
(69th percentile)

Weaknesses

CVE ID

CVE-2017-7660

GHSA ID

GHSA-c82r-qg3w-q5mv

Source code

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