cve.bz

CVE-2013-6397 apache solr: Path traversal

no score yetExploit referenceEPSS 57%Fix available

apache solr: no CVSS score yet. EPSS 57% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.solr:solr-core 4.6.0.

On this page
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.
EPSS
57% (unchanged from 57% a week ago; 56% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2013-6397 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-6397?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-6397?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2013-6397 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
apache:solrthrough 4.5.1
apache:solr4.0.0
apache:solr4.0.0:alpha
apache:solr4.0.0:beta
apache:solr4.1.0
apache:solr4.2.0
apache:solr4.2.1
apache:solr4.3.0
apache:solr4.3.1
apache:solr4.4.0
apache:solr4.5.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j8qw-mwmv-28cgMavenorg.apache.solr:solr-core<4.6.04.6.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian7lucene-solr3.6.0+dfsg-1+deb7u1DSA-2963-1
Debian12, 13, 14lucene-solr3.6.2+dfsg-2DEBIAN-CVE-2013-6397

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat JBoss Data Grid 6.2Fixed 2014-01-15RHSA-2014:0029
Red Hat JBoss Web Framework Kit 2.4Fixed 2013-12-16RHSA-2013:1844
Red Hat JBoss Data Grid 6solrAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2013-6397.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET WEB_SERVER Apache Solr Arbitrary XSLT inclusion attack (CVE-2013-6397) sid 2017882

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON