CVE-2021-21973 is a server-side request forgery vulnerability in the vSphere Client (HTML5) of VMware vCenter Server, caused by improper validation of URLs in a vCenter Server plugin associated with the VMware vROPS Client integration. A remote attacker with network access to the vCenter Server HTTPS service on port 443 can send a crafted POST request to the vulnerable plugin endpoint and induce the server to make unintended requests. The issue affects VMware vCenter Server 7.x before 7.0 U1c, 6.7 before 6.7 U3l, and 6.5 before 6.5 U3n, as well as VMware Cloud Foundation 4.x before 4.2 and 3.x before 3.10.1.2. Successful exploitation leads to information disclosure via SSRF.
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.
com.vmware.vrops.install to incompatible; merely disabling the plugin in the UI is not sufficient. In vCenter High Availability deployments, the workaround must be applied to both active and passive nodes.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.
2 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.
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.