The vSphere Client (HTML5) contains a remote code execution vulnerability due to lack of input validation in the Virtual SAN Health Check pl
VMware vCenter Server and VMware Cloud Foundation are exposed by default, even without vSAN, via the Virtual SAN Health Check plug-in. Fixes are listed in the Response Matrix (KB83829).
- 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
The vSphere Client (HTML5) in VMware vCenter Server, specifically its Virtual SAN Health Check plug-in, which is enabled by default, is affected. An attacker with network access to port 443 could run arbitrary commands with unrestricted privileges on the operating system hosting vCenter Server.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The vSphere Client (HTML5) contains a remote code execution vulnerability due to lack of input validation in the Virtual SAN Health Check plug-in which is enabled by default in vCenter Server. A malicious actor with network access to port 443 may exploit this issue to execute commands with unrestricted privileges on the underlying operating system that hosts vCenter Server.
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 and VMware Cloud Foundation
VMware vCenter Server (7.x before 7.0 U2b, 6.7 before 6.7 U3n, 6.5 before 6.5 U3p) and VMware Cloud Foundation (4.x before 4.2.1, 3.x before 3.10.2.1)
References 3
Questions about CVE-2021-21985
What does this mean?
Missing input validation in the Virtual SAN Health Check plug-in of the vSphere Client (HTML5) allows commands to be run remotely with unrestricted privileges on the operating system that hosts vCenter Server.Source: support.broadcom.com
Am I affected, and how do I check?
The advisory names VMware vCenter Server and VMware Cloud Foundation. The affected plug-in is enabled by default in all vCenter Server deployments, whether or not vSAN is used. Readers can compare their vCenter Server version against the Response Matrix in KB83829.Source: support.broadcom.com
What should I do about it?
Apply the updates listed in the 'Fixed Version' column of the Response Matrix in KB83829 to affected deployments.Source: support.broadcom.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, 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?
The advisory points to workarounds listed in the Response Matrix in KB83829. Readers should follow those workarounds until a fixed version is applied.Source: support.broadcom.com