CVE-2018-1274 is a high-severity (CVSS 7.5) CWE-770 vulnerability in org.springframework.data:spring-data-commons. A fix is available for org.springframework.data:spring-data-commons — see the affected versions and patch details below.
Spring Data Commons contain a property path parser vulnerability caused by unlimited resource allocation
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commonsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring 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).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-commons | all versions | 1.13.11org.springframework.data:spring-data-commons:1.13.11 |
| ☕Maven | org.springframework.data:spring-data-commons | ≥ 2.0.0&&< 2.0.6 | 2.0.6org.springframework.data:spring-data-commons:2.0.6 |
Affected Products
spring data commonsbroadcomspring data restpivotal_softwarespring data restvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.data:spring-data-commons to 1.13.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1274 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2018-1274 in your dependencies?
Find it across Maven, including transitive dependencies.