dbcve.org
SolrApplication · Apache

CVE-2017-3164

HIGH · 7.5 CVSS v3.0 Published 2019-03-08
Fix available
A fix is available. Upgrade to after 7.6.0 or later.
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
Server Side Request Forgery in Apache Solr, versions 1.3 until 7.6 (inclusive). Since the "shards" parameter does not have a corresponding whitelist mechanism, a remote attacker with access to the server could make Solr perform an HTTP GET request to any reachable URL.

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 versions 1.3 through 7.6 contain a Server Side Request Forgery (SSRF) vulnerability via the 'shards' parameter. Since this parameter lacks a corresponding whitelist mechanism, an attacker with access to the Solr server can induce it to make HTTP GET requests to arbitrary URLs, potentially exfiltrating data from internal services or pivoting to internal network targets.

MitigationImplement a whitelist of allowed hosts/domains for the 'shards' parameter in Solr configuration, or upgrade to Apache Solr 7.7 or later which includes the fix for this vulnerability.

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:>= 1.3.0, <= 7.6.0

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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 'solr -v' or 'bin/solr -v' from the Solr installation directory, or check the VERSION.txt file in the Solr home directory, or access the Solr Admin UI and look for the version number displayed on the main page
    Affected if The installed version is between 1.3.0 and 7.6.0 inclusive
  2. Confirm Solr admin endpoint is network-accessible
    Check if the Solr admin interface (port 8983 by default) is bound to a non-localhost address or is reachable from network segments outside your trust boundary. Review Solr configuration in solr.in.sh or solr.in.cmd for SOLR_HOST setting
    Affected if The Solr admin interface is accessible from untrusted networks without authentication
  3. Verify 'shards' parameter handling in Solr requests
    Review your Solr query patterns and any custom request handlers to determine if the 'shards' parameter is used or could be supplied in search requests. Check distributed search configurations in solrconfig.xml
    Affected if The 'shards' parameter can be supplied in requests to your Solr instance without restriction
  4. Check for network segmentation of Solr service
    Review firewall rules, network ACLs, or cloud security groups to determine if the Solr port (default 8983) is exposed to the internet or to untrusted internal network segments
    Affected if Solr is reachable from network segments that should not have access
  5. Audit Solr authentication configuration
    Examine whether Solr's authentication is enabled by checking for the presence of security.json in ZooKeeper or the Solr home directory, or by verifying ENABLE_AUTHENTICATION settings in solr.in.sh
    Affected if No authentication is configured for the Solr admin interface or API endpoints

You are affected if your Solr version is between 1.3.0 and 7.6.0 and the server is accessible to attackers who can send requests with arbitrary 'shards' parameter values.

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
Upgrade available Upgrade to a release after 7.6.0
Interim mitigation

Implement a whitelist of allowed hosts/domains for the 'shards' parameter in Solr configuration, or upgrade to Apache Solr 7.7 or later which includes the fix for this vulnerability.

Fix this in Solr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3164 — 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-3164 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