CVE-2021-21973 is a server-side request forgery vulnerability in the HTML5 vSphere Client component of VMware vCenter Server. Improper validation of URLs processed by a vCenter Server plugin permits an unauthenticated network attacker to cause the server to issue attacker-influenced requests. Affected versions are VMware vCenter Server 7.x before 7.0 U1c, 6.7 before 6.7 U3l, and 6.5 before 6.5 U3n; VMware Cloud Foundation 4.x before 4.2 and 3.x before 3.10.1.2 are also affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A VMware vCenter Server vulnerability addressed via VMSA-2021-0002, with a documented workaround that requires setting the VMware vROPS Client plugin to incompatible rather than merely disabling it in the UI.
A VMware vCenter Server remote code execution vulnerability abused in malicious cryptocurrency-mining campaigns.
An SSRF vulnerability in a cloud platform that has been exploited in the wild.
An SSRF vulnerability in a cloud platform that the content states has been exploited in the wild.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.