Skip to content

← Public intelligence

Maven package

org.springframework:spring-oxm

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedMavenPublished

    Cross-Site Request Forgery in Spring Framework

    CVE-2013-4152 · GHSA-rp4p-g69r-438x

    Affected
    • Maven org.springframework:spring-oxm <= 3.2.3.RELEASE
    Fixed in
    3.2.4.RELEASE· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.2.4.RELEASE or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedMavenPublished

    Missing XML Validation in Spring Framework

    CVE-2013-7315 · GHSA-vp63-rrcm-9mph

    Affected
    • Maven org.springframework:spring-oxm <= 3.2.3.RELEASE
    Fixed in
    3.2.4.RELEASE· Vendor fix available
    Issue
    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 XMLInputFactory, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML with JAXB, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152. NOTE: this issue was SPLIT from CVE-2013-4152 due to different affected versions.

    Recommended action: Upgrade to 3.2.4.RELEASE or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →