# CVE-2014-0225: Improper Restriction of XML External Entity Reference in Spring Framework

> Attackers can exploit XML External Entity vulnerabilities in Spring Framework to read sensitive files or cause denial of service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0225, GHSA-f93f-g33r-8pcp, MGASA-2015-0211, ROOT-APP-MAVEN-CVE-2014-0225, UBUNTU-CVE-2014-0225

## What is CVE-2014-0225?

CVE-2014-0225 is a high-severity vulnerability in Vmware Spring Framework, published on 25 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

When processing user provided XML documents, the Spring Framework 4.0.0 to 4.0.4, 3.0.0 to 3.2.8, and possibly earlier unsupported versions did not disable by default the resolution of URI references in a DTD declaration. This enabled an XXE attack.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

4 open source packages ship an affected version, including org.springframework:spring-webmvc. It affects 2 products.


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

Products: Pivotal Software Spring Framework, Vmware Spring Framework.

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

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

## Is CVE-2014-0225 being exploited?

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

## Other vulnerabilities in Vmware Spring Framework

- [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)
- [CVE-2015-0201](https://insights.sbomify.com/CVE-2015-0201/): Moderate severity vulnerability that affects org.springframework:spring-core (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0225 is a high-severity vulnerability in Vmware Spring Framework, published on 25 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-0225 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework:spring-webmvc (Maven): affected from 3.0.0; fixed in 3.2.8
- org.springframework:spring-webmvc (Maven): affected from 3.0.0; fixed in 3.2.8
- org.springframework:spring-webmvc (Maven): affected from 4.0.0; fixed in 4.0.5
- org.springframework:spring-webmvc (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-0225/ (Markdown: https://insights.sbomify.com/CVE-2014-0225/index.md)
```

## Sources

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

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