CVE intelligence and bounded remediation

CVE-2017-7660 — Apache Solr uses a PKI based mechanism to secure inter-node communication when security is enabled

High CVSS 7.5

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.

Severity
High
CVSS
7.5 (3.0)
Published
2017-07-07
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-287

Affected products

  • apache / solr / 5.3.0
  • apache / solr / 5.3.1
  • apache / solr / 5.3.2
  • apache / solr / 5.4.0
  • apache / solr / 5.4.1
  • apache / solr / 5.5.0

Showing 6 representative product identities from 21 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Authentication bypass and missing authentication

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
  • Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
  • Review session, token, credential, and proxy trust configuration without attempting account takeover.

Remediate safely

  • Apply the supported fix and centralize fail-closed authentication before protected request handling.
  • Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
  • Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.