# CVE-2014-3578: Improper Limitation of a Pathname to a Restricted Directory in Spring Framework

> Remote attackers can read arbitrary files via crafted URLs in Spring Framework, requiring an upgrade to secure the application.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3578, GHSA-rhcg-rwhx-qj3j, UBUNTU-CVE-2014-3578

## What is CVE-2014-3578?

CVE-2014-3578 is a medium-severity path traversal vulnerability in n/a, published on 19 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Pivotal Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5 allows remote attackers to read arbitrary files via a crafted URL.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2014-3578?

4 open source packages ship an affected version, including org.springframework:spring-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework:spring-core` | Maven | From 3.0.0 | 3.2.9 |
| `org.springframework:spring-core` | Maven | From 3.0.0 | 3.2.9 |
| `org.springframework:spring-core` | Maven | From 4.0.0 | 4.0.5 |
| `org.springframework:spring-core` | Maven | From 4.0.0 | 4.0.5 |

Products: Pivotal Software Spring Framework.

## How do I fix CVE-2014-3578?

Upgrade org.springframework:spring-core to a fixed version for your release line: 3.2.9 or 4.0.5.

## Is CVE-2014-3578 being exploited?

There is no known exploitation of CVE-2014-3578 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-0225](https://insights.sbomify.com/CVE-2014-0225/): Improper Restriction of XML External Entity Reference in Spring Framework (high 8.8)
- [CVE-2016-5007](https://insights.sbomify.com/CVE-2016-5007/): Spring Security and Spring Framework may not recognize certain paths that should be protected (high 7.5)
- [CVE-2016-9878](https://insights.sbomify.com/CVE-2016-9878/): Pivotal Spring Framework Paths provided to the ResourceServlet were not properly sanitized (high 7.5)
- [CVE-2013-6429](https://insights.sbomify.com/CVE-2013-6429/): Cross-Site Request Forgery in Spring Framework (medium 6.8)
- [CVE-2013-6430](https://insights.sbomify.com/CVE-2013-6430/): Improper Neutralization of Input During Web Page Generation in Spring Framework (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3578 and fix it if it is affected.

What it is: CVE-2014-3578 is a medium-severity path traversal vulnerability in n/a, published on 19 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3578 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework:spring-core (Maven): affected from 3.0.0; fixed in 3.2.9
- org.springframework:spring-core (Maven): affected from 3.0.0; fixed in 3.2.9
- org.springframework:spring-core (Maven): affected from 4.0.0; fixed in 4.0.5
- org.springframework:spring-core (Maven): affected from 4.0.0; fixed in 4.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-3578/ (Markdown: https://insights.sbomify.com/CVE-2014-3578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-3578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-3578
- OSV: https://osv.dev/vulnerability/CVE-2014-3578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-3578/
Summaries are generated and may contain mistakes; the official description above is the record.