Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2013-4152: 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…

MediumCVSS 6.8 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 25.6% (FIRST EPSS); higher than 97.9% of all records.
  • Fixed version: libspring-java (Debian:12) 3.0.6.RELEASE-10; libspring-java (Debian:7) 3.0.6.RELEASE-6+deb7u1; org.springframework:spring-oxm (Maven) 3.2.4.RELEASE.

Low priority for now. Upgrade to libspring-java (Debian:12) 3.0.6.RELEASE-10; libspring-java (Debian:7) 3.0.6.RELEASE-6+deb7u1; org.springframework:spring-oxm (Maven) 3.2.4.RELEASE or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.6% · 97th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

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

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2013-4152

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

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

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-103.0.6.RELEASE-10
Debian:7libspring-javabefore 3.0.6.RELEASE-6+deb7u13.0.6.RELEASE-6+deb7u1
Mavenorg.springframework:spring-oxmbefore 3.2.4.RELEASE3.2.4.RELEASE
Red Hat:openshift:2.0::el6activemqbefore 0:5.9.0-4.redhat.610328.el6op0:5.9.0-4.redhat.610328.el6op
Red Hat:openshift:2.0::el6activemq-clientbefore 0:5.9.0-4.redhat.610328.el6op0:5.9.0-4.redhat.610328.el6op

Other 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…
    54Plan
  • 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…
    40Plan
  • 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…
    34Monitor

Published before and after this one in the same product

  • Later →CVE-2013-7315Jan 23, 2014 · The 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…
    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-10 · Debian:12Package registry (OSV)
Maven:org.springframework:spring-oxm3.2.4.RELEASEPackage registry (OSV)
red hat:activemq0:5.9.0-4.redhat.610328.el6op · Red Hat:openshift:2.0::el6Package registry (OSV)
red hat:activemq-client0:5.9.0-4.redhat.610328.el6op · Red Hat:openshift:2.0::el6Package 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.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

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

    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.

    References

    All records