Skip to content
Noroxi
CVE-2014-0054· NVD / CVE Program· CNA redhat

The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external ent

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.

MediumCVSS 6.8 · v2.0—No exploit Fix available
Published
Apr 17, 2014
Updated
Jun 16, 2026
EPSS
91.4% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

54

Plan

Add it to your regular patch cycle.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
27 / 30 · 91.4%

Affected systems

VendorProduct
springsourcespring framework
vmwarespring 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
  • springsource spring framework3.2.5
  • springsource spring framework3.2.6
  • springsource spring framework4.0.0
  • springsource spring framework4.0.1
  • vmware spring frameworkup to 3.2.7 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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libspring-javabefore 3.0.6.RELEASE-133.0.6.RELEASE-13
Debian:7libspring-javabefore 3.0.6.RELEASE-6+deb7u33.0.6.RELEASE-6+deb7u3
Mavenorg.springframework:spring-webmvcfrom 4.0.0 · before 4.0.24.0.2
Mavenorg.springframework:spring-webmvcbefore 3.2.83.2.8

Other highest-scoring records for the same primary product.

  • 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 a
    40Plan
  • CVE-2013-4152The 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
    35Monitor
  • 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 (E
    34Monitor
  • 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 XMLIn
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Debian:libspring-java3.0.6.RELEASE-13 · Debian:12Package registry (OSV)
Maven:org.springframework:spring-webmvc3.2.8Package registry (OSV)
Maven:org.springframework:spring-webmvc4.0.2Package 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.

EPSS, last 120 days

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.

No commit or PR link among the references.

Finders, 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

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:P/A:P

    nvd-primary

    Root cause

    State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

    Fixed

    ts
    app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    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 help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records