Spring Data RestFramework / library · VMware
CVE-2018-1273
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 · uneditedSpring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack.
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 confidenceA property binder vulnerability in Spring Data Commons allows unauthenticated remote attackers to execute arbitrary code by crafting malicious request parameters that exploit the property binding mechanism in Spring Data REST resources or projection-based request payload binding.
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
<= 2.5.10>= 2.6.0, <= 2.6.10
IgniteApplication
>= 1.0.1, <= 2.5.0= 1.0.0<= 1.12.10>= 1.13.0, <= 1.13.10>= 2.0.0, <= 2.0.5>= 3.0.0, <= 3.0.5= 8.0.8.2.0= 8.0.8.3.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Data dependency presenceReview project build files (pom.xml, build.gradle) or JAR manifest for spring-data-commons or spring-data-rest artifactsAffected if The vulnerability only applies if Spring Data Commons or Spring Data Rest is included as a dependency
-
Determine exact version of Spring Data libraryExtract the version from pom.xml, build.gradle, or the MANIFEST.MF file within the deployed spring-data-commons or spring-data-rest JARAffected if The installed version must be compared against known vulnerable ranges to confirm exposure
-
Verify version against affected rangesCompare your installed version to: Broadcom Spring Data Commons <=1.12.10, 1.13.0-1.13.10, or 2.0.0-2.0.5; VMware Spring Data Rest <=2.5.10 or 2.6.0-2.6.10; Pivotal Software Spring Data Rest 3.0.0-3.0.5; Apache Ignite 1.0.0 or 1.0.1-2.5.0; Oracle Financial Services Crime And Compliance Management Studio 8.0.8.2.0 or 8.0.8.3.0Affected if Your version falls within any of these ranges means you are running a vulnerable release
-
Confirm Spring Data REST is enabledCheck application code for @RepositoryRestResource annotations on repository interfaces, or inspect application.properties/yml for spring.data.rest.base-uri or similar REST configurationAffected if Spring Data REST is enabled and exposes HTTP resources, which is required for the attack surface
-
Check for projection or parameter binding usageSearch code for @Projection annotations on interfaces, or examine controllers/repositories that accept request parameters bound directly to object propertiesAffected if The application uses projections or binds request parameters to domain object properties, which enables the malicious payload injection
You are affected if your application uses a vulnerable Spring Data Commons or Spring Data Rest version AND exposes REST endpoints or accepts user-controlled request parameters that bind to domain objects.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Spring Data Commons to version 1.13.10+, 2.0.5+, or later. If immediate patching is not feasible, disable Spring Data REST endpoints or implement strict input validation on all request parameters.
Spring Data Commons: 1.13.11+ or 2.0.6+ | Spring Data Rest: 2.6.11+ or 3.0.6+ | Apache Ignite: 2.5.1+
- 1. Identify all applications using Spring Data Commons or Spring Data REST in your environment
- 2. For Spring Data Commons: Upgrade to version 1.13.11 or later (for 1.x branch) OR version 2.0.6 or later (for 2.x branch)
- 3. For Spring Data Rest: Upgrade to version 2.6.11 or later (for 2.x branch) OR version 3.0.6 or later (for 3.x branch)
- 4. If using Apache Ignite: Upgrade to version 2.5.1 or later to receive the patched Spring Data dependencies
- 5. Rebuild and redeploy all affected applications with the fixed Spring Data versions
- 6. Verify the upgrade by testing Spring Data REST endpoints with the projection and property binding features
- 7. For Oracle Financial Services Crime and Compliance Management Studio: Apply the April 2018 Critical Patch Update from Oracle (CPUApr2018)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Data Rest
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation2.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1273 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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