CVE-2018-1274

Spring Data Commons contain a property path parser vulnerability caused by unlimited resource allocation

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).

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2018-1274 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.13.11, 2.0.6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2018-1274? CVE-2018-1274 is a high-severity allocation of resources without limits or throttling vulnerability in org.springframework.data:spring-data-commons (maven), affecting versions < 1.13.11. It is fixed in 1.13.11, 2.0.6. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2018-1274? CVE-2018-1274 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.springframework.data:spring-data-commons are affected by CVE-2018-1274? org.springframework.data:spring-data-commons (maven) versions < 1.13.11 is affected.
4. Is there a fix for CVE-2018-1274? Yes. CVE-2018-1274 is fixed in 1.13.11, 2.0.6. Upgrade to this version or later.
5. Is CVE-2018-1274 exploitable, and should I be worried? Whether CVE-2018-1274 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2018-1274 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2018-1274?
   • Upgrade org.springframework.data:spring-data-commons to 1.13.11 or later
   • Upgrade org.springframework.data:spring-data-commons to 2.0.6 or later

Other vulnerabilities in org.springframework.data:spring-data-commons