# Improper Limitation of a Pathname to a Restricted Directory in Apache Solr

Advisory record · `GHSA-j8qw-mwmv-28cg`

- **Identifiers:** `GHSA-j8qw-mwmv-28cg` · `CVE-2013-6397`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 17 May 2022
- **Updated:** 30 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 04:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.solr:solr-core` (Maven): affected `<4.6.0`; fixed in `4.6.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Solr (org.apache.solr:solr-core) versions before 4.6.0 are affected. A remote attacker can send a crafted request to the select handler using the XSLT response writer to read arbitrary files on the server through a directory traversal flaw. The source notes this can be combined with a separate XML external entity vulnerability to reach files across restricted network boundaries. Upgrade to version 4.6.0 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.57, the 99th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j8qw-mwmv-28cg)

## Sources

- [GitHub Advisory Database: GHSA-j8qw-mwmv-28cg](https://github.com/advisories/GHSA-j8qw-mwmv-28cg)
- [OSV: GHSA-j8qw-mwmv-28cg](https://osv.dev/vulnerability/GHSA-j8qw-mwmv-28cg)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-6397>
- <https://github.com/apache/lucene-solr/commit/da34b18cb3092df4972e2b6fa5178d1059923910>
- <https://github.com/apache/lucene-solr>
- <https://issues.apache.org/jira/browse/SOLR-4882>
- <https://web.archive.org/web/20170307173358/http://www.securityfocus.com/bid/63935>
- <http://lucene.apache.org/solr/4_6_0/changes/Changes.html>
- <http://rhn.redhat.com/errata/RHSA-2013-1844.html>
- <http://rhn.redhat.com/errata/RHSA-2014-0029.html>
- <http://www.agarri.fr/kom/archives/2013/11/27/compromising_an_unreachable_solr_server_with_cve-2013-6397/index.html>
- <http://www.openwall.com/lists/oss-security/2013/11/27/1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j8qw-mwmv-28cg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j8qw-mwmv-28cg/>. Everything for agents: <https://agentprime.io/llms.txt>.
