Threats / VMware Tanzu / CVE-2018-1273
CVE-2018-1273
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
VMware Tanzu Spring Data Commons vulnerability
Spring Data Commons property binder vulnerability allows remote code execution through unsafe object binding, enabling attackers to execute arbitrary code on affected systems.
Verdict
Today item, not a backlog item.
A critical remote code execution flaw in Spring Data Commons property binding mechanisms permits unauthenticated attackers to execute arbitrary code. Active exploitation and ransomware deployment have been observed in the wild.
CISA KEV Yes · 2022-03-253Ransomware use Flagged3EPSS 0.95649 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
691 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.95649 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: VMware Tanzu, Spring Data Commons. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request containing code-execution payloads targeting the property binder.
Business
Attacker gains code execution capability on the vulnerable application server.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I establish persistence and lateral movement within the compromised infrastructure.
Business
Attacker expands foothold across internal systems and data repositories.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or exfiltrate sensitive data from the organization.
Business
Operations halt, data confidentiality is breached, and ransom demands or regulatory fines follow.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05