CVE-2021-21985: The vSphere Client (HTML5) contains a remote code execution vulnerability due to lack of input validation i...
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.
Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated attacker who can reach vCenter Server on port 443 run commands with unrestricted operating-system privileges. Compromise could expose or disrupt centralized virtual infrastructure management. The vulnerable Virtual SAN Health Check plug-in is enabled by default.
Executive priority
Treat as an immediate remediation priority because exploitation is documented, authentication is unnecessary, and successful compromise grants unrestricted host operating-system privileges. Prioritize reachable management servers and investigate potentially exposed systems rather than assuming patching alone excludes earlier compromise.
Technical view
CVE-2021-21985 is an input-validation failure in the vSphere Client's Virtual SAN Health Check plug-in. It enables network-based, low-complexity remote code execution without privileges or user interaction. CVSS 3.1 rates it 9.8, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure exists where affected vCenter Server or VMware Cloud Foundation versions are deployed and attackers can reach vCenter Server port 443. Internet exposure increases concern, but internal network access is also sufficient. The supplied evidence does not identify individual exposed organizations.
Exploitation context
CISA includes CVE-2021-21985 in its Known Exploited Vulnerabilities catalog, supporting active exploitation in the wild. The supplied sources do not establish current exploitation volume, specific threat actors, targeting patterns, or compromise indicators.
Researcher notes
The supplied classification identifies CWE-20, CWE-470, and CWE-918. The evidence establishes default plug-in enablement, port 443 reachability, unauthenticated command execution, affected version boundaries, and KEV status. It does not provide reliable exploit-chain details, indicators, or attribution.
Mitigation direction
Update vCenter 7.x to 7.0 U2b or later.
Update vCenter 6.7 to 6.7 U3n or later.
Update vCenter 6.5 to 6.5 U3p or later.
Update Cloud Foundation 4.x to 4.2.1 or later.
Update Cloud Foundation 3.x to 3.10.2.1 or later.
Restrict port 443 access to trusted management networks while remediation is pending.
Validation and detection
Inventory all vCenter Server and VMware Cloud Foundation deployments.
Compare installed versions against every affected-version boundary.
Confirm port 443 reachability from untrusted and ordinary internal networks.
Verify applicable updates completed successfully on each instance.
Consult vendor guidance for available compromise indicators and post-update checks.
The source record changed after analysis: Material source record changed after analysis.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
n/aVMware vCenter Server and VMware Cloud FoundationVMware 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)Listed
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.