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, wh
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.
- Published
- Jan 23, 2014
- Updated
- Jun 16, 2026
- EPSS
- 25.5% · 98th percentile
- CWE
- CWE-264
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 8 / 30 · 25.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| springsource | spring framework | cpe:2.3:a:springsource:spring_framework |
| vmware | spring framework | cpe:2.3:a:vmware:spring_framework |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- springsource spring framework3.0.0
- springsource spring framework3.0.0.m1
- springsource spring framework3.0.0.m2
- springsource spring framework3.0.1
- springsource spring framework3.0.2
- springsource spring framework3.0.3
- springsource spring framework3.0.4
- springsource spring framework3.0.5
- vmware spring frameworkup to 3.2.3 inclusive
- vmware spring framework3.0.6
- vmware spring framework3.0.7
- vmware spring framework3.1.0
- vmware spring framework3.1.1
- vmware spring framework3.1.2
- vmware spring framework3.1.3
- vmware spring framework3.1.4
- vmware spring framework3.2.0
- vmware spring framework3.2.1
- vmware spring framework3.2.2
- vmware spring framework4.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libspring-java | before 3.0.6.RELEASE-10 | 3.0.6.RELEASE-10 |
| Debian:7 | libspring-java | before 3.0.6.RELEASE-6+deb7u1 | 3.0.6.RELEASE-6+deb7u1 |
| Maven | org.springframework:spring-oxm | before 3.2.4.RELEASE | 3.2.4.RELEASE |
| Red Hat:openshift:2.0::el6 | activemq | before 0:5.9.0-4.redhat.610328.el6op | 0:5.9.0-4.redhat.610328.el6op |
| Red Hat:openshift:2.0::el6 | activemq-client | before 0:5.9.0-4.redhat.610328.el6op | 0:5.9.0-4.redhat.610328.el6op |
Same product
springsource: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0054The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external ent54Plan
- CVE-2010-1622SpringSource Spring Framework 2.5.x before 2.5.6.SEC02, 2.5.7 before 2.5.7.SR01, and 3.0.x before 3.0.3 allows remote attackers to execute a40Plan
- CVE-2011-2730VMware SpringSource Spring Framework before 2.5.6.SEC03, 2.5.7.SR023, and 3.x before 3.0.6, when a container supports Expression Language (E34Monitor
- CVE-2013-7315The Spring MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external entity resolution for the StAX XMLIn29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Debian:libspring-java | 3.0.6.RELEASE-10 · Debian:12 | Package registry (OSV) |
| Maven:org.springframework:spring-oxm | 3.2.4.RELEASE | Package registry (OSV) |
| Red Hat:activemq | 0:5.9.0-4.redhat.610328.el6op · Red Hat:openshift:2.0::el6 | Package registry (OSV) |
| Red Hat:activemq-client | 0:5.9.0-4.redhat.610328.el6op · Red Hat:openshift:2.0::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- rhn.redhat.com/errata/RHSA-2014-0212.html
- rhn.redhat.com/errata/RHSA-2014-0245.html
- rhn.redhat.com/errata/RHSA-2014-0254.html
- rhn.redhat.com/errata/RHSA-2014-0400.html
- seclists.org/bugtraq/2013/Aug/154
- seclists.org/fulldisclosure/2013/Nov/14
- secunia.com/advisories/56247
- secunia.com/advisories/57915
- www.debian.org/security/2014/dsa-2842
- www.gopivotal.com/security/cve-2013-4152
- www.securityfocus.com/bid/61951
- github.com/spring-projects/spring-framework/pull/317/files
Vendor advisories and official records. Exploit/PoC links are deliberately left out.