CVE-2013-4152 — spring-oxm
Fix: spring-projects/spring-framework#317CVE-2013-4152 is a CWE-264 vulnerability in org.springframework:spring-oxm. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.springframework:spring-oxm — see the affected versions and patch details below.
Cross-Site Request Forgery in Spring Framework
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.springframework:spring-oxmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via an XML external entity declaration in conjunction with an entity reference in a (1) DOMSource, (2) StAXSource, (3) SAXSource, or (4) StreamSource, aka an XML External Entity (XXE) issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-oxm | all versions | 3.2.4.RELEASEorg.springframework:spring-oxm:3.2.4.RELEASE |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-oxm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-oxm to 3.2.4.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4152 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-4152 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2013-4152. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss A-MQ 6.1 | see advisory | RHSA-2014:0401 |
| Red Hat JBoss Fuse 6.1 | see advisory | RHSA-2014:0400 |
| Red Hat JBoss SOA Platform 5.3 | spring | RHSA-2014:0212 |
| Red Hat OpenShift Enterprise 2.0 | activemq-0:5.9.0-4.redhat.610328.el6op | RHSA-2014:0245 |
| RHEL 6 Version of OpenShift Enterprise 1.2 | activemq-0:5.9.0-4.redhat.610328.el6op | RHSA-2014:0254 |
Frequently Asked Questions
Is CVE-2013-4152 in your dependencies?
O3 Security finds CVE-2013-4152 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.