CVE-2017-3163

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 6.6% (93rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
41
EG Risk 41/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation7% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
6.6%
EPSS %ILE
93rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 30, 2017

Last Modified

June 17, 2026

References (14)

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsolr-core2018-05-14redhat
redhatpicketbox-0:4.1.7-1.Final_redhat_1.1.ep6.el52018-05-14redhat
redhatpicketbox-0:4.1.7-1.Final_redhat_1.1.ep6.el72018-05-14redhat
redhatjboss-ec2-eap-0:7.5.20-1.Final_redhat_1.ep6.el62018-05-14redhat
redhatpicketbox-0:4.1.7-1.Final_redhat_1.1.ep6.el62018-05-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.0+dfsg-1, 3.6.0+dfsg-1+deb7u1
  • every version up to 3.6.0+dfsg-1+deb7u2: fixed in 3.6.0+dfsg-1+deb7u2
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-5
  • every version up to 3.6.2+dfsg-5+deb8u1: fixed in 3.6.2+dfsg-5+deb8u1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-10
  • every version up to 3.6.2+dfsg-10+deb9u1: fixed in 3.6.2+dfsg-10+deb9u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.solr:solr-core6.0.0 ... 6.4.0 (7 versions)
  • every version up to 5.5.4: fixed in 5.5.4
  • 6.0.0 up to 6.4.1: fixed in 6.4.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-10-09 20:02 UTCEPSS rescore
  2. 2026-10-08 16:36 UTCEPSS rescore
  3. 2026-10-08 01:05 UTCOSV refresh
  4. 2026-10-07 23:41 UTCEPSS rescore
  5. 2026-10-06 15:12 UTCEPSS rescore
  6. 2026-10-05 17:38 UTCEPSS rescore
  7. 2026-10-04 23:18 UTCEPSS rescore
  8. 2026-10-03 14:21 UTCEPSS rescore
  9. 2026-09-30 14:59 UTCEPSS rescore
  10. 2026-09-30 09:33 UTCEG score recompute
  11. 2026-09-28 13:45 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-27 13:40 UTCEPSS rescore
  14. 2026-09-26 15:53 UTCEPSS rescore
  15. 2026-09-24 13:59 UTCEPSS rescore
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-18 07:06 UTCOSV refresh
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-15 03:05 UTCEPSS rescore
  21. 2026-09-13 16:42 UTCEPSS rescore
  22. 2026-09-12 14:55 UTCEPSS rescore
  23. 2026-09-11 09:31 UTCEPSS rescore
  24. 2026-09-07 15:56 UTCEPSS rescore
  25. 2026-09-06 13:43 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:23 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-02 14:07 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 03:31 UTCEPSS rescore
  6. 2026-08-30 19:13 UTCEPSS rescore
  7. 2026-08-30 07:30 UTCOSV refresh
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:41 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-21 23:44 UTCEPSS rescore
  12. 2026-08-20 22:51 UTCEPSS rescore
  13. 2026-08-19 16:59 UTCEPSS rescore
  14. 2026-08-18 13:43 UTCEPSS rescore
  15. 2026-08-16 14:51 UTCEPSS rescore
  16. 2026-08-16 02:10 UTCEPSS rescore
  17. 2026-08-15 01:26 UTCEPSS rescore
  18. 2026-08-13 22:49 UTCOSV refresh
  19. 2026-08-12 13:46 UTCEPSS rescore
  20. 2026-08-09 13:42 UTCEPSS rescore
  21. 2026-08-07 16:22 UTCEPSS rescore
  22. 2026-08-06 13:42 UTCEPSS rescore
  23. 2026-08-05 19:12 UTCEPSS rescore
  24. 2026-08-04 15:05 UTCEPSS rescore
  25. 2026-08-02 02:23 UTCEPSS rescore
  26. 2026-08-01 04:11 UTCEPSS rescore
  27. 2026-07-30 16:24 UTCEPSS rescore
  28. 2026-07-30 01:26 UTCEPSS rescore
  29. 2026-07-29 01:51 UTCOSV refresh
  30. 2026-07-28 15:32 UTCEPSS rescore
  31. 2026-07-26 14:51 UTCEPSS rescore
  32. 2026-07-23 14:15 UTCEPSS rescore
  33. 2026-07-23 01:29 UTCEG score recompute
  34. 2026-07-22 22:08 UTCEG score recompute
  35. 2026-07-22 14:04 UTCEPSS rescore
  36. 2026-07-22 14:04 UTCEPSS rescore
  37. 2026-07-21 15:21 UTCEPSS rescore
  38. 2026-07-21 15:21 UTCEPSS rescore
  39. 2026-07-20 17:04 UTCEPSS rescore
  40. 2026-07-19 14:28 UTCEPSS rescore
  41. 2026-07-19 14:28 UTCEPSS rescore
  42. 2026-07-19 02:26 UTCEPSS rescore
  43. 2026-07-19 02:26 UTCEPSS rescore
  44. 2026-07-18 10:00 UTCEPSS rescore
  45. 2026-07-16 16:59 UTCEPSS rescore
  46. 2026-07-16 16:59 UTCEPSS rescore
  47. 2026-07-15 16:54 UTCEPSS rescore
  48. 2026-07-15 01:56 UTCEPSS rescore
  49. 2026-07-15 01:56 UTCEPSS rescore
  50. 2026-07-13 22:26 UTCEPSS rescore
  51. 2026-07-12 05:43 UTCEPSS rescore
  52. 2026-07-11 18:22 UTCOSV refresh
  53. 2026-07-11 08:24 UTCEPSS rescore
  54. 2026-07-09 19:06 UTCEPSS rescore
  55. 2026-07-08 15:10 UTCEPSS rescore
  56. 2026-07-07 13:42 UTCEPSS rescore
  57. 2026-07-06 16:24 UTCEPSS rescore
  58. 2026-07-06 16:24 UTCEPSS rescore
  59. 2026-07-06 02:20 UTCEPSS rescore
  60. 2026-07-06 02:20 UTCEPSS rescore
  61. 2026-07-05 02:27 UTCEPSS rescore
  62. 2026-07-04 06:28 UTCEPSS rescore
  63. 2026-07-02 16:54 UTCEPSS rescore
  64. 2026-07-01 15:02 UTCEPSS rescore
  65. 2026-06-30 23:19 UTCEPSS rescore
  66. 2026-06-30 23:19 UTCEPSS rescore
  67. 2026-06-29 14:03 UTCEPSS rescore
  68. 2026-06-28 14:04 UTCEPSS rescore
  69. 2026-06-28 04:53 UTCEPSS rescore
  70. 2026-06-27 03:06 UTCEPSS rescore
  71. 2026-06-27 03:05 UTCEPSS rescore
  72. 2026-06-25 13:47 UTCEPSS rescore
  73. 2026-06-24 14:02 UTCEPSS rescore
  74. 2026-06-24 14:02 UTCEPSS rescore
  75. 2026-06-23 21:30 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-3163?
CVE-2017-3163 is a high vulnerability published on August 30, 2017. 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…
When was CVE-2017-3163 disclosed?
CVE-2017-3163 was first published on August 30, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-3163 actively exploited?
CVE-2017-3163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.6% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-3163?
CVE-2017-3163 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-3163?
A fix for CVE-2017-3163 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-3163

Explore →

Is Your Infrastructure Affected by CVE-2017-3163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs