dbcve.org
Spring Data RestFramework / library · VMware

CVE-2018-1259

HIGH · 7.5 CVSS v3.0 Published 2018-05-11
Fix available
A fix is available. Upgrade to after 3.0.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Spring Data Commons, versions 1.13 prior to 1.13.12 and 2.0 prior to 2.0.7, used in combination with XMLBeam 1.4.14 or earlier versions, contains a property binder vulnerability caused by improper restriction of XML external entity references as underlying library XMLBeam does not restrict external reference expansion. An unauthenticated remote malicious user can supply specially crafted request parameters against Spring Data's projection-based request payload binding to access arbitrary files on the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring Data Commons versions prior to 1.13.12 and 2.0.7, when combined with XMLBeam 1.4.14 or earlier, contains an XXE (XML External Entity) vulnerability. The XMLBeam library fails to restrict external entity references, allowing attackers to exploit Spring Data's projection-based request payload binding to read arbitrary files from the server filesystem.

MitigationUpgrade Spring Data Commons to version 1.13.12+ or 2.0.7+ and XMLBeam to a version that properly restricts external entities. Alternatively, disable external entity processing in the XML parser configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Data RestFramework / library
Affected:> 2.6, <= 2.6.11
Spring Data CommonsFramework / library
Affected:>= 1.13, <= 1.13.11>= 2.0, <= 2.0.6
Spring Data RestFramework / library
Affected:>= 3.0, <= 3.0.6
XmlbeamApplication
Affected:<= 1.4.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Data Commons version
    Inspect your project's dependency management file (pom.xml or build.gradle) for the spring-data-commons artifact version, or examine the JAR file's MANIFEST.MF. For Maven, run: mvn dependency:tree | grep spring-data-commons
    Affected if Version is 1.13.0 through 1.13.11, or 2.0.0 through 2.0.6
  2. Identify XMLBeam version
    Inspect pom.xml or build.gradle for the xmlbeam artifact version, or check the XMLBeam JAR version in your lib or dependencies folder
    Affected if Version is 1.4.14 or earlier AND Spring Data Commons is in the affected range
  3. Verify Spring Data REST is in use
    Check pom.xml or build.gradle for spring-data-rest-webmvc or spring-data-rest dependencies, or look for @RepositoryRestResource annotations in your codebase
    Affected if Spring Data REST is present with version 2.6.x (2.6.1-2.6.11), 3.0.x (3.0.1-3.0.6), or similar affected versions alongside vulnerable Spring Data Commons
  4. Confirm XML projection capability is enabled
    Look for @Projection definitions with XML support in your codebase, or check if your Spring Data REST application accepts XML content types (application/xml) in controller mappings or configuration
    Affected if XML-based projections or XML request body handling for Spring Data REST repositories is configured

You are affected if Spring Data Commons is version 1.13.0-1.13.11 or 2.0.0-2.0.6 AND XMLBeam version 1.4.14 or earlier is present in your classpath, combined with Spring Data REST handling XML payloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3.0.6
Interim mitigation

Upgrade Spring Data Commons to version 1.13.12+ or 2.0.7+ and XMLBeam to a version that properly restricts external entities. Alternatively, disable external entity processing in the XML parser configuration.

Fix this in Spring Data Rest Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1259 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data