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 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: 2017-08-30 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-3163 is rated Moderate Risk (57.5/100): CVSS High severity, with high exploitation likelihood (EPSS 6.56%, 93th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-3163

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 11.86% 6.56% -5.30%
2 2026-04-29 16.45% 11.86% -4.59%
3 2026-03-04 — 16.45% —

Full EPSS history (37 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-3163

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2017-3163

GitHub Security Advisory for CVE-2017-3163

GHSA-387v-84cv-9qmc · Severity: high · Ecosystem: maven — Improper Limitation of a Pathname ('Path Traversal') in org.apache.solr:solr-core

OS Trackers for CVE-2017-3163

vendor priority summary link
debian not yet assigned CVE-2017-3163 not yet assigned priority: Debian including 1 source packages (lucene-solr), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-3163
redhat medium — https://access.redhat.com/security/cve/CVE-2017-3163
ubuntu medium CVE-2017-3163 medium priority: Ubuntu including 1 source packages (lucene-solr), 22 status rows across 22 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 16, ignored 2, released 2, needed 1, needs-triage 1. https://ubuntu.com/security/CVE-2017-3163

Affected software / configurations for CVE-2017-3163

Vendor Product Version Raw CPE
apache solr <= 5.5.3 cpe:2.3:a:apache:solr:*:*:*:*:*:*:*:*
apache solr 6.0.0 cpe:2.3:a:apache:solr:6.0.0:*:*:*:*:*:*:*
apache solr 6.0.1 cpe:2.3:a:apache:solr:6.0.1:*:*:*:*:*:*:*
apache solr 6.1.0 cpe:2.3:a:apache:solr:6.1.0:*:*:*:*:*:*:*
apache solr 6.2.0 cpe:2.3:a:apache:solr:6.2.0:*:*:*:*:*:*:*
apache solr 6.2.1 cpe:2.3:a:apache:solr:6.2.1:*:*:*:*:*:*:*
apache solr 6.3.0 cpe:2.3:a:apache:solr:6.3.0:*:*:*:*:*:*:*
apache solr 6.4.0 cpe:2.3:a:apache:solr:6.4.0:*:*:*:*:*:*:*

References for CVE-2017-3163

cvelogic Threat Intelligence