SolrApplication · Apache
CVE-2017-3163
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 · uneditedWhen using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.
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 confidencePath traversal vulnerability in Apache Solr's Index Replication feature where the HTTP API for pulling index files from master/leader nodes did not validate file names, allowing attackers to use path traversal sequences (../) to read arbitrary files accessible to the Solr server process.
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
<= 5.5.3= 6.0.0= 6.0.1= 6.1.0= 6.2.0= 6.2.1= 6.3.0= 6.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Solr versionQuery the Solr API endpoint /solr/admin/info/system or check the solr-core jar file metadata in the installation directoryAffected if The version is 5.5.3 or lower, or 6.0.0 through 6.4.0 inclusive (not 5.5.4 or 6.4.1 or later)
-
Verify Index Replication feature is configuredCheck if a replication handler is defined in solrconfig.xml (look for <requestHandler name="/replication" class="solr.ReplicationHandler">) or if replication is enabled in solr.xml for any coreAffected if Index Replication is enabled and a replication handler is actively configured
-
Confirm HTTP API is accessibleTest network access to Solr's HTTP API endpoints (such as /solr/<core>/replication) from untrusted networks or verify no firewall or authentication restricts accessAffected if The HTTP API is reachable without proper firewall restrictions or authentication
-
Check for path traversal protectionReview solrconfig.xml for any input validation filters or path sanitization on the replication handler, or test with a crafted request containing ../ sequences to the replication APIAffected if The replication handler accepts path traversal sequences without validation (vulnerable state)
You are affected if your Solr version falls within 5.5.3 or lower, or 6.0.0-6.4.0, AND the Index Replication feature is enabled with the HTTP API accessible to untrusted clients.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Solr 5.5.4 or 6.4.1 or later which includes proper file name validation, and ensure Solr servers are protected by firewall rules and/or authentication to limit HTTP access to trusted clients.
Fix this in Solr
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3163 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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