CVE-2013-6397

MEDIUMCVSS v2 · 4.34.3
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:P/I:N/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 56.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 56%
CISA-KEV: Not listedEPSS PROB: 56%CVSS v2: 4.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Directory traversal vulnerability in SolrResourceLoader in Apache Solr before 4.6 allows remote attackers to read arbitrary files via a .. (dot dot) or full pathname in the tr parameter to solr/select/, when the response writer (wt parameter) is set to XSLT. NOTE: this can be leveraged using a separate XXE (XML eXternal Entity) vulnerability to allow access to files across restricted network boundaries.

CVSS v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3(low)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

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
Severity43% × 45%
Exploitation56% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
56%
EPSS %ILE
99%
KEV
Not listed

Published

December 7, 2013

Last Modified

April 29, 2026

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2014-01-15redhat
redhatpatch2013-12-16redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.solr:solr-core1.3.0 ... 4.5.1 (22 versions)4.6.0

All Vendor Advisories

(2)

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 11× in last 7d / 27× 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.

  1. 2026-07-26 13:49 UTCEG score recompute 4.30
  2. 2026-07-23 14:14 UTCEPSS rescore
  3. 2026-07-23 01:11 UTCEG score recompute 4.30
  4. 2026-07-23 00:14 UTCEG score recompute 4.30
  5. 2026-07-22 21:53 UTCEG score recompute 9.00
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-22 09:07 UTCOSV refresh
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-20 17:03 UTCEPSS rescore
  11. 2026-07-20 17:03 UTCEPSS rescore
  12. 2026-07-19 02:25 UTCEPSS rescore
  13. 2026-07-16 16:58 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-13 22:26 UTCEPSS rescore
  17. 2026-07-13 06:08 UTCEPSS rescore
  18. 2026-07-12 05:42 UTCEPSS rescore
  19. 2026-07-09 19:05 UTCEPSS rescore
  20. 2026-07-05 04:21 UTCOSV refresh
  21. 2026-07-05 02:26 UTCEPSS rescore
  22. 2026-07-04 06:27 UTCEPSS rescore
  23. 2026-07-02 15:21 UTCEPSS rescore
  24. 2026-07-01 15:02 UTCEPSS rescore
  25. 2026-06-30 23:19 UTCEPSS rescore
Show 42 more
  1. 2026-06-28 04:53 UTCEPSS rescore
  2. 2026-06-28 04:53 UTCEPSS rescore
  3. 2026-06-27 03:05 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-21 01:57 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-16 17:49 UTCEPSS rescore
  18. 2026-06-16 17:49 UTCEPSS rescore
  19. 2026-06-16 15:43 UTCOSV refresh
  20. 2026-06-15 17:44 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-13 22:57 UTCEPSS rescore
  23. 2026-06-12 23:08 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-10 13:18 UTCEPSS rescore
  26. 2026-06-08 14:14 UTCEPSS rescore
  27. 2026-06-05 22:44 UTCEPSS rescore
  28. 2026-06-05 22:44 UTCEPSS rescore
  29. 2026-06-02 20:10 UTCEPSS rescore
  30. 2026-06-02 20:10 UTCEPSS rescore
  31. 2026-05-28 21:23 UTCEG score recompute
  32. 2026-05-28 21:23 UTCVendor advisory
  33. 2026-05-28 20:36 UTCOSV refresh
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-26 07:16 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 22:37 UTCEPSS rescore
  41. 2026-05-18 21:29 UTCEPSS rescore
  42. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2013-6397?
CVE-2013-6397 is a medium vulnerability published on December 7, 2013. Directory traversal vulnerability in SolrResourceLoader in Apache Solr before 4.6 allows remote attackers to read arbitrary files via a .. (dot dot) or full pathname in the tr parameter to solr/select/, when the response writer (wt parameter) is set to XSLT. NOTE: this can be leveraged using a…
When was CVE-2013-6397 disclosed?
CVE-2013-6397 was first published in the National Vulnerability Database on December 7, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-6397 actively exploited?
CVE-2013-6397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 56% probability of exploitation in the next 30 days, which ranks it in the top 1.0% of all scored CVEs.
How do I remediate CVE-2013-6397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-6397, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-6397

Explore →

Is Your Infrastructure Affected by CVE-2013-6397?

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