CVE-2018-1273
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.
- CVSS
- 9.8Criticalscored by CISA
- Exploited in the wild
- Yes, in CISA KEV since 25 Mar 2022CISA deadline for US federal agencies: 15 Apr 2022known use in ransomware campaignsunvetted proof-of-concept code on github
- EPSS
- 97.0%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 11 Apr 2018analysed here 12 Nov 2026
Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Spring by Pivotal Spring Framework | Versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versionsVendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- broadcom:spring_data_commons
- pivotal_software:spring_data_rest
- vmware:spring_data_rest
- apache:ignite
- oracle:financial_services_crime_and_compliance_management_studio
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.
Also consider: remove eval sinks · RASP
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 25 Mar 2022. Known use in ransomware campaigns.
- CISA due date
- 15 Apr 2022, the remediation deadline for US federal agencies
- CISA required action
- Apply updates per vendor instructions.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 7 GitHub proofs of concept · 1 Nuclei template
- CISA SSVC
- exploitation active, automatable yes, technical impact totalAssessed by CISA 11 Mar 2022 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Nuclei
- Spring Data Commons - Remote Code Executiondetection template, critical
GitHub proofs of concept
- jas502n/cve-2018-127358 stars
- wearearima/poc-cve-2018-127324 stars
- knqyf263/CVE-2018-127310 stars
- webr0ck/poc-cve-2018-12732 stars
and 3 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 11 Apr 2018Published
- 13 Apr 2018First proof-of-concept repository on GitHub (unvetted)1 day later
- 11 Mar 2022CISA SSVC assessment: exploitation active1,428 days (about 4 years) later
- 25 Mar 2022Added to CISA KEV (exploited in the wild)14 days later
- 15 Apr 2022CISA remediation due date (US federal agencies)21 days later
- 26 Aug 2026CVE record last updated1,594 days (about 4 years) later
- 12 Nov 2026Analysed by vulneraibility.com78 days (about 3 months) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2018-1273 being exploited?
Yes. CVE-2018-1273 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2018-1273?
CVE-2018-1273 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2018-1273?
Yes. A fix has been recorded for CVE-2018-1273. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2018-1273 affect?
CVE-2018-1273 affects broadcom:spring_data_commons, pivotal_software:spring_data_rest, vmware:spring_data_rest, apache:ignite, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
4 references in the CVE record, grouped by the tags the record gives them.
Other links (4)
- mail-archives.apache.org /mod_mbox/ignite-dev/201807.mbox/%3CCAK0qHnqzfzmCDFFi6c5Jok19zNkVCz5Xb4sU%3D0f2J
- oracle.com /security-alerts/cpujul2022.html
- pivotal.io /security/cve-2018-1273
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-1273
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.