How to check if you are exposed to CVE-2018-1273
- Find every VMware Tanzu Spring Data Commons system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
- Compare each version with the fixed versions in the vendor advisory. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
- Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2018-1273.
US federal agencies had to fix this by 2022-04-15. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.
Affected versions
Versions the National Vulnerability Database lists as vulnerable to CVE-2018-1273. Check the vendor advisory for the exact fixed builds before you sign anything off.
| Product | Vulnerable versions |
|---|---|
| Broadcom Spring Data Commons | up to and including 1.12.10; from 1.13.0 up to and including 1.13.10; from 2.0.0 up to and including 2.0.5 |
| Pivotal Software Spring Data Rest | from 3.0.0 up to and including 3.0.5 |
| Vmware Spring Data Rest | up to and including 2.5.10; from 2.6.0 up to and including 2.6.10 |
| Apache Ignite | from 1.0.1 up to and including 2.5.0; 1.0.0; 1.0.0-rc3 |
| Oracle Financial Services Crime AND Compliance Management Studio | 8.0.8.2.0; 8.0.8.3.0 |
Timeline
- · Published in the National Vulnerability Database
- · Added to CISA's Known Exploited Vulnerabilities catalog, 1,444 days after it was published
- · Fix-by date for US federal agencies, passed 1,661 days ago
Weakness type
More exploited VMware Tanzu vulnerabilities
CISA lists 3 exploited VMware Tanzu vulnerabilities. The closest matches:
Keep going
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.