dbcve.org
SolrApplication · Apache

CVE-2017-7660

HIGH · 7.5 CVSS v3.0 Published 2017-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Solr uses PKI-based inter-node authentication when security is enabled. Attackers can create a specially crafted node name that does not exist in the cluster and point it to a malicious node, tricking legitimate nodes into accepting the malicious node as a valid cluster member. This affects servers using BasicAuthPlugin or custom authentication plugins that do not implement HttpClientInterceptorPlugin or HttpClientBuilderPlugin.

MitigationImplement HttpClientInterceptorPlugin or HttpClientBuilderPlugin in custom authentication plugins to properly validate inter-node communication, or upgrade to a patched Apache Solr version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolrApplication
Affected:= 5.3.0= 5.3.1= 5.3.2= 5.4.0= 5.4.1= 5.5.0= 5.5.1= 5.5.2= 5.5.3= 5.5.4= 6.0.0= 6.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Solr version
    Run `bin/solr version` or check the solr WAR file version in the Solr distribution. Alternatively, query the Solr API at `http://localhost:8983/solr/admin/info/system` and look for the 'solr-impl' or 'version' field.
    Affected if The installed version matches any of: 5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.4.1, 5.5.0, 5.5.1, 5.5.2, 5.5.3, 5.5.4, 6.0.0, or 6.0.1.
  2. Verify Solr security is enabled
    Check for the presence of security.json in ZooKeeper at `/solr/security.json` or in Solr's conf directory. Also check if BasicAuth is configured by querying `http://localhost:8983/solr/admin/authentication` or reviewing the security.json content.
    Affected if Security is enabled and BasicAuthPlugin or a custom authentication plugin is configured.
  3. Determine the authentication plugin type
    Examine the security.json file (retrieve via `curl http://localhost:8983/solr/admin/authentication` or from ZooKeeper) and look at the 'authentication' section to identify the plugin class in use.
    Affected if The plugin class is 'BasicAuthPlugin' or a custom authentication plugin (not the standard Solr authentication).
  4. Check if custom plugin implements required interfaces
    Review the source code or JAR file of any custom authentication plugin to determine if it implements `HttpClientInterceptorPlugin` or `HttpClientBuilderPlugin` interfaces. These are required for proper inter-node communication validation.
    Affected if A custom authentication plugin is in use AND it does NOT implement HttpClientInterceptorPlugin or HttpClientBuilderPlugin.

You are affected if you run Apache Solr version 5.3.0 through 6.0.1 with security enabled using BasicAuthPlugin or a custom authentication plugin that lacks HttpClientInterceptorPlugin or HttpClientBuilderPlugin implementation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement HttpClientInterceptorPlugin or HttpClientBuilderPlugin in custom authentication plugins to properly validate inter-node communication, or upgrade to a patched Apache Solr version.

Fix this in Solr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7660 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data