CVE-2017-3163: When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a…
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6.5% (FIRST EPSS); higher than 93.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: lucene-solr (Debian:12) 3.6.2+dfsg-11; lucene-solr (Debian:7) 3.6.0+dfsg-1+deb7u2; lucene-solr (Debian:8) 3.6.2+dfsg-5+deb8u1.
Low priority for now. Upgrade to lucene-solr (Debian:12) 3.6.2+dfsg-11; lucene-solr (Debian:7) 3.6.0+dfsg-1+deb7u2; lucene-solr (Debian:8) 3.6.2+dfsg-5+deb8u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
When 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.
- Published
- Aug 30, 2017
- Updated
- Jun 16, 2026
- EPSS
- 6.5% · 93th percentile
- CWE
- CWE-22
Report tools
Action score
32
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | solr | cpe:2.3:a:apache:solr |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Solr
- 1.4.0 to 5.5.3, 6.0.0 to 6.4.0affected
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache solrup to 5.5.3 inclusive
- apache solr6.0.0
- apache solr6.0.1
- apache solr6.1.0
- apache solr6.2.0
- apache solr6.2.1
- apache solr6.3.0
- apache solr6.4.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | lucene-solr | before 3.6.2+dfsg-11 | 3.6.2+dfsg-11 |
| Debian:7 | lucene-solr | before 3.6.0+dfsg-1+deb7u2 | 3.6.0+dfsg-1+deb7u2 |
| Debian:8 | lucene-solr | before 3.6.2+dfsg-5+deb8u1 | 3.6.2+dfsg-5+deb8u1 |
| Debian:9 | lucene-solr | before 3.6.2+dfsg-10+deb9u1 | 3.6.2+dfsg-10+deb9u1 |
| Maven | org.apache.solr:solr-core | from 6.0.0 · before 6.4.1 | 6.4.1 |
| Maven | org.apache.solr:solr-core | before 5.5.4 | 5.5.4 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | codehaus-jackson | before 0:1.9.9-12.redhat_6.1.ep6.el5 | 0:1.9.9-12.redhat_6.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | codehaus-jackson-core-asl | before 0:1.9.9-12.redhat_6.1.ep6.el5 | 0:1.9.9-12.redhat_6.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | codehaus-jackson-jaxrs | before 0:1.9.9-12.redhat_6.1.ep6.el5 | 0:1.9.9-12.redhat_6.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | codehaus-jackson-mapper-asl | before 0:1.9.9-12.redhat_6.1.ep6.el5 | 0:1.9.9-12.redhat_6.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | codehaus-jackson-xc | before 0:1.9.9-12.redhat_6.1.ep6.el5 | 0:1.9.9-12.redhat_6.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | hornetq | before 0:2.3.25-26.SP24_redhat_1.1.ep6.el5 | 0:2.3.25-26.SP24_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-appclient | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-cli | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-client-all | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-clustering | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-cmp | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-configadmin | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-connector | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-controller | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-controller-client | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-core-security | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-deployment-repository | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | jboss-as-deployment-scanner | before 0:7.5.20-1.Final_redhat_1.1.ep6.el5 | 0:7.5.20-1.Final_redhat_1.1.ep6.el5 |
+96
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-17558Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter.KEV90Now
- CVE-2019-0193In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in…KEV83Now
- CVE-2024-45216Apache Solr: Authentication bypass possible using a fake URL Path ending67This week
Published before and after this one in the same product
- ← EarlierCVE-2015-8797Feb 14, 2016 · Cross-site scripting (XSS) vulnerability in webapp/web/js/scripts/plugins.js in the stats page in the Admin UI in Apache Solr before 5.3.1…25Monitor
- ← EarlierCVE-2017-7660Jul 7, 2017 · Apache Solr uses a PKI based mechanism to secure inter-node communication when security is enabled.32Monitor
- Later →CVE-2017-9803Sep 18, 2017 · Apache Solr's Kerberos plugin can be configured to use delegation tokens, which allows an application to reuse the authentication of an…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:lucene-solr | 3.6.2+dfsg-11 · Debian:12 | Package registry (OSV) |
| Maven:org.apache.solr:solr-core | 5.5.4 | Package registry (OSV) |
| Maven:org.apache.solr:solr-core | 6.4.1 | Package registry (OSV) |
| red hat:codehaus-jackson | 0:1.9.9-12.redhat_6.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:codehaus-jackson-core-asl | 0:1.9.9-12.redhat_6.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:codehaus-jackson-jaxrs | 0:1.9.9-12.redhat_6.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:codehaus-jackson-mapper-asl | 0:1.9.9-12.redhat_6.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:codehaus-jackson-xc | 0:1.9.9-12.redhat_6.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:hornetq | 0:2.3.25-26.SP24_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:jboss-as-appclient | 0:7.5.20-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:jboss-as-cli | 0:7.5.20-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:jboss-as-client-all | 0:7.5.20-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:jboss-as-clustering | 0:7.5.20-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:jboss-as-cmp | 0:7.5.20-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
| red hat:jboss-as-configadmin | 0:7.5.20-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- access.redhat.com/errata/RHSA-2018:1448
- access.redhat.com/errata/RHSA-2018:1449
- access.redhat.com/errata/RHSA-2018:1450
- access.redhat.com/errata/RHSA-2018:1451
- lists.apache.org/thread.html/a6a33a186f293f9f9aecf3bd39c76252bfc49a79de4321dd2a53b488%40%3Csolr-user.lucene.apache.org%3E
- www.debian.org/security/2018/dsa-4124
Vendor advisories and official records. Exploit/PoC links are deliberately left out.