Spring Data RestFramework / library · VMware
CVE-2018-1274
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 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property path parser vulnerability caused by unlimited resource allocation. An unauthenticated remote malicious user (or attacker) can issue requests against Spring Data REST endpoints or endpoints using property path parsing which can cause a denial of service (CPU and memory consumption).
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 confidenceSpring Data Commons versions 1.13-1.13.10 and 2.0-2.0.5 contain a property path parser vulnerability where the parser does not limit resource allocation. An unauthenticated remote attacker can send specially crafted requests to Spring Data REST endpoints or any endpoint using property path parsing, causing excessive CPU and memory consumption leading to denial of service.
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.6, <= 2.6.10< 1.13.11>= 2.0.0, < 2.0.6>= 3.0, <= 3.0.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Commons or Spring Data REST dependencyCheck your project build file (pom.xml, build.gradle) for 'spring-data-commons' or 'spring-data-rest' dependencies. Run 'mvn dependency:tree' or 'gradle dependencies' to list all Spring Data dependencies and their versions.Affected if The dependency version falls within: spring-data-commons < 1.13.11 or >= 2.0.0 to < 2.0.6; spring-data-rest 2.6.x to 2.6.10; or spring-data-rest 3.0.x to 3.0.5
-
Confirm Spring Data REST endpoints are exposedCheck your application configuration and code for @RepositoryRestResource annotations or Spring Data REST auto-configuration. Review your application's API endpoints to determine if any REST endpoints are exposing Spring Data repositories.Affected if Spring Data REST endpoints are accessible without authentication and the vulnerable library version is in use
-
Verify property path parsing is in useReview your application for usage of Spring Data's PropertyPath class, QueryDSL integration, or any custom repository methods that accept property path parameters. Check if your application exposes any query parameters that could be interpreted as property paths.Affected if Property path parsing features are enabled and accessible via HTTP endpoints, combined with a vulnerable version
-
Check application runtime versionAt runtime, check the JAR file version in your deployment or run: java -cp spring-data-commons-*.jar META-INF/MANIFEST.MF, or inspect the version reported in application logs during startup.Affected if The running spring-data-commons JAR matches the vulnerable version ranges listed
Your environment is affected if Spring Data Commons (version < 1.13.11 or >= 2.0.0 to < 2.0.6) or Spring Data REST (2.6.x to 2.6.10 or 3.0.x to 3.0.5) is in use AND Spring Data REST endpoints or property path parsing features are exposed over the network.
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.
From vendor data1.13.112.0.6
Upgrade Spring Data Commons to version 1.13.11, 2.0.6, or later. If immediate upgrading is not feasible, implement rate limiting and network-level restrictions on Spring Data REST endpoints to mitigate exploitation.
Fix this in Spring Data Rest
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1274 — 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-1274 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