# CVE-2018-1273: VMware Tanzu Spring Data Commons Property Binder

> Unauthenticated attackers can achieve remote code execution via crafted request parameters in Spring Data Commons property binding.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2018
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-4fq3-mr56-cg6r

## What is CVE-2018-1273?

CVE-2018-1273 is a critical code injection vulnerability in Spring Framework, published on 11 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2018-1273?

4 open source packages ship an affected version, including org.springframework.data:spring-data-commons. It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.data:spring-data-commons` | Maven | From 1.13.0 | 1.13.11 |
| `org.springframework.data:spring-data-commons` | Maven | From 1.13.0 | 1.13.11 |
| `org.springframework.data:spring-data-commons` | Maven | From 2.0.0 | 2.0.6 |
| `org.springframework.data:spring-data-commons` | Maven | From 2.0.0 | 2.0.6 |

Products: Apache Ignite, Broadcom Spring Data Commons, Oracle Financial Services Crime and Compliance Management Studio, Pivotal Software Spring Data Rest, Vmware Spring Data Rest.

## How do I fix CVE-2018-1273?

Upgrade org.springframework.data:spring-data-commons to a fixed version for your release line: 1.13.11 or 2.0.6. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2018-1273 being exploited?

Yes. Attackers have exploited CVE-2018-1273 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Spring Data Commons RCE 远程命令执行漏洞 (github_poc): https://github.com/jas502n/cve-2018-1273
- POC for CVE-2018-1273 (github_poc): https://github.com/wearearima/poc-cve-2018-1273
- Environment for CVE-2018-1273 (Spring Data Commons) (github_poc): https://github.com/knqyf263/CVE-2018-1273
- https://github.com/webr0ck/poc-cve-2018-1273 (github_poc): https://github.com/webr0ck/poc-cve-2018-1273
- cve-2018-1273 (github_poc): https://github.com/cved-sources/cve-2018-1273
- https://github.com/hdgokani/CVE-2018-1273 (github_poc): https://github.com/hdgokani/CVE-2018-1273

## Other vulnerabilities in Spring Framework

- [CVE-2018-8018](https://insights.sbomify.com/CVE-2018-8018/): Code execution via deserialization in org.apache.ignite:ignite-core (critical 9.8)
- [CVE-2018-1295](https://insights.sbomify.com/CVE-2018-1295/): Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization (critical 9.8)
- [CVE-2024-52577](https://insights.sbomify.com/CVE-2024-52577/): Apache Ignite: Possible RCE when deserializing incoming messages by the server node (critical 9.5)
- [CVE-2020-1963](https://insights.sbomify.com/CVE-2020-1963/): File system access via H2 in Apache Ignite (critical 9.1)
- [CVE-2025-48977](https://insights.sbomify.com/CVE-2025-48977/): Apache Ignite: REST HTTP arbitrary file read vulnerability (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1273 and fix it if it is affected.

What it is: CVE-2018-1273 is a critical code injection vulnerability in Spring Framework, published on 11 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-1273 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

Affected packages and fixed versions:
- org.springframework.data:spring-data-commons (Maven): affected from 1.13.0; fixed in 1.13.11
- org.springframework.data:spring-data-commons (Maven): affected from 1.13.0; fixed in 1.13.11
- org.springframework.data:spring-data-commons (Maven): affected from 2.0.0; fixed in 2.0.6
- org.springframework.data:spring-data-commons (Maven): affected from 2.0.0; fixed in 2.0.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1273/ (Markdown: https://insights.sbomify.com/CVE-2018-1273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1273
- OSV: https://osv.dev/vulnerability/CVE-2018-1273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1273/
Summaries are generated and may contain mistakes; the official description above is the record.