SSRF in VMware vCenter Server vROPS Client Plugin
CVE-2021-21973 is a server-side request forgery vulnerability in the VMware vROPS Client plugin exposed through the vSphere Client HTML5 interface. Improper validation of URLs allows a remote attacker with network access to TCP port 443 to submit a crafted POST request that causes vCenter Server to make HTTP requests to attacker-selected destinations, potentially disclosing information. Affected releases are VMware vCenter Server 7.x before 7.0 U1c, 6.7 before 6.7 U3l, and 6.5 before 6.5 U3n, and VMware Cloud Foundation 4.x before 4.2 and 3.x before 3.10.1.2.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can disclose information from the vulnerable application or backend systems reachable by vCenter Server. Requests originate from the server, potentially exposing resources that the attacker cannot access directly. Arbitrary code execution and full system compromise are not established consequences of this vulnerability alone.
If you can’t patch tonight, do this now.
If patching is delayed, apply VMware KB 82374: back up the vSphere UI compatibility matrix, add the entry <PluginPackage id="com.vmware.vrops.install" status="incompatible"/>, and restart the vsphere-ui service. This workaround applies to both Linux-based vCenter Server Appliance and Windows deployments. In vCenter High Availability environments, apply it to both active and passive nodes. Verify that the plugin appears as incompatible and that its checkmobregister endpoint returns HTTP 404. Merely disabling the plugin through the UI does not protect the system.
Patch, then assume compromise.
Apply the VMware fixes documented in VMSA-2021-0002. Upgrade vCenter Server to 7.0 U1c, 6.7 U3l, or 6.5 U3n, as appropriate, or a later fixed release. Upgrade affected VMware Cloud Foundation deployments to 4.2 or 3.10.1.2, as appropriate, or a later fixed release.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.