Vulnerability record · CVE-2014-0054 · published 17 April 2014
CVE-2014-0054: Spring Framework Jaxb2RootElementHttpMessageConverter XXE flaw
SSpringsource · Spring Framework
The Jaxb2RootElementHttpMessageConverter in Spring MVC does not disable external entity resolution, allowing crafted XML to trigger an XML External Entity (XXE) issue. This is an incomplete fix for CVE-2013-4152, CVE-2013-7315, and CVE-2013-6429, so systems patched for those earlier issues may still be exposed.
Description
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External Entity (XXE) issue. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-4152, CVE-2013-7315, and CVE-2013-6429.
AV:N/AC:M/Au:N/C:P/I:P/A:P
Automated analysis
high priorityThe flaw allows file disclosure, denial of service, and CSRF, and EPSS indicates a very high probability of exploitation activity, though no KEV listing or public exploit reference is present.
What it is
The Jaxb2RootElementHttpMessageConverter in Spring MVC does not disable external entity resolution, allowing crafted XML to trigger an XML External Entity (XXE) issue. This is an incomplete fix for CVE-2013-4152, CVE-2013-7315, and CVE-2013-6429, so systems patched for those earlier issues may still be exposed.
Impact
A remote attacker can read arbitrary files, cause a denial of service, and conduct CSRF attacks. The CVSS 2.0 vector shows partial confidentiality, integrity, and availability impact.
Attack surface
Reached over the network via crafted XML submitted to a Spring MVC endpoint that uses Jaxb2RootElementHttpMessageConverter. The CVSS vector indicates no authentication is required, though attack complexity is medium.
Exploitation
Not listed in CISA KEV and no ransomware associations are documented. EPSS is very high at 0.91354 (99.8th percentile), but the record contains no reference tags indicating a public exploit.
What to do
- Upgrade Spring Framework to 3.2.8 or later, or 4.0.2 or later, which contain the complete fix.
- If immediate upgrade is not possible, disable external entity resolution in the XML parser used by Jaxb2RootElementHttpMessageConverter.
- Apply vendor errata such as RHSA-2014-0400 where applicable.
- Review and restrict XML endpoints that accept untrusted input.
Detection
- Monitor for XML payloads containing DOCTYPE declarations or external entity references sent to Spring MVC endpoints.
- Alert on unexpected outbound network connections or file reads originating from the application server.
- Audit Spring Framework versions in use to identify deployments below 3.2.8 or 4.0.2.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2014-0054 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2014-0054), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.