The vSphere Client (HTML5) contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in a vCenter Serv
Affects vCenter Server 7.0 before U1c, 6.7 before U3l and 6.5 before U3n, and VMware Cloud Foundation 4.x before 4.2. CVSS scores it 5.3 (medium); no vendor rating is given. Fixed in the listed updates.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
VMware vCenter Server and VMware Cloud Foundation, through the vSphere Client's HTML5 interface and a vCenter Server plugin, are affected. An attacker with network access to the server could send a specially crafted request that causes it to disclose sensitive information.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The vSphere Client (HTML5) contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in a vCenter Server plugin. A malicious actor with network access to port 443 may exploit this issue by sending a POST request to vCenter Server plugin leading to information disclosure. This affects: 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).
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- n/a VMware vCenter Server
7.x before 7.0 U1c, 6.7 before 6.7 U3l, 6.5 before 6.5 U3n
- n/a VMware Cloud Foundation
4.x before 4.2, 3.x before 3.10.1.2
References 1
vmware.com
Questions about CVE-2021-21973
What does this mean?
The vSphere Client (HTML5) vROPs plugin does not properly validate URLs, so the vCenter Server can be made to send server-side requests it should not send. This leads to information disclosure.Source: support.broadcom.com
Am I affected, and how do I check?
Affected are vCenter Server 7.0 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. The vROPs plugin is present in all default installations, so compare the vCenter Server version in its version information against these ranges.Source: support.broadcom.com
What should I do about it?
Apply the updates listed in the Fixed Version column of the Response Matrix to affected deployments, which means moving to vCenter Server 7.0 U1c, 6.7 U3l or 6.5 U3n, or to VMware Cloud Foundation 4.2 or later.Source: support.broadcom.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-07, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data
What if there's no patch?
Follow the workarounds listed in the Response Matrix (KB82374), which advise disabling the plugin endpoint until the updates can be applied.Source: support.broadcom.com