CVE-2021-21973: VMware vCenter Server and Cloud Foundation Server Side Request Forgery (SSRF)
VMware vCenter Server and Cloud Foundation · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-07.
- CVSS v3.1 (CISA ADP)
- 5.3
- medium
- EPSS (exploit probability, 30 days)
- 88%
- higher than 99.7% of all CVEs
- Added to CISA KEV
- 2022-03-07
- US federal due date 2022-03-21
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2021-21973 explained
CVE-2021-21973 is a server-side request forgery (SSRF) flaw in the vSphere Client (HTML5) of VMware vCenter Server and VMware Cloud Foundation. A vCenter Server plugin does not properly validate URLs, so an unauthenticated attacker with network access can trigger information disclosure. CISA lists it as known to be exploited.
Impact
An attacker who can reach port 443 on vCenter Server can send a crafted POST request to a vulnerable plugin and cause information disclosure. No credentials or user interaction are needed. CISA rates the flaw as automatable, meaning it can be exploited at scale, with partial technical impact. Confidentiality impact is limited; integrity and availability are not affected. Attackers are known to exploit this vulnerability.
Who is affected
The CVE record describes affected versions in free text. VMware vCenter Server: 7.x before 7.0 U1c, 6.7 before 6.7 U3l and 6.5 before 6.5 U3n. VMware Cloud Foundation: 4.x before 4.2 and 3.x before 3.10.1.2. The CVE record names no fixed version in its fixed-version data; confirm the correct update for each branch in the VMware advisory.
Written with AI from the data on this page and checked against it automatically.
Official 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).
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- VMware vCenter ServerAffectedFixed in
- 7.x before 7.0 U1c
- 6.7 before 6.7 U3l
- 6.5 before 6.5 U3n
not statedVersion statement as published by the CNA (free text).
- VMware Cloud FoundationAffectedFixed in
- 4.x before 4.2
- 3.x before 3.10.1.2
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| VMware vCenter ServerVersion statement as published by the CNA (free text). |
| not stated |
| VMware Cloud FoundationVersion statement as published by the CNA (free text). |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: vmware.com/security/advisories/VMSA-2021-0002.html
- CISA's deadline for US federal agencies: 2022-03-21 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify all vCenter Server and Cloud Foundation deployments and their versions.
- Apply updates per VMware's instructions, as CISA's required action states.
- Confirm in the VMware advisory which release fixes your branch, beyond the versions named in the affected ranges.
- Restrict access to vCenter Server port 443 to trusted management networks and keep it off the internet.
- Review vCenter Server logs for unusual POST requests to plugins and other signs of compromise.
The CVE record lists no fixed version in its structured data. Follow the VMware advisory to find the update for your branch and apply it, as CISA requires. Until updated, limit network access to vCenter Server port 443 to trusted administrators and apply any workaround VMware documents.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Partial – limited control or information
Weakness: CWE-918 Server-Side Request Forgery (SSRF)
Questions about CVE-2021-21973
- Is this vulnerability exploited in the wild?
- Yes. CISA added CVE-2021-21973 to its Known Exploited Vulnerabilities catalog on 2022-03-07, with a US federal due date of 2022-03-21. Known ransomware use is listed as unknown.
- Does an attacker need credentials?
- No. The CVSS data shows no privileges and no user interaction are required. Network access to port 443 on vCenter Server is enough.
- What can an attacker gain?
- The flaw leads to information disclosure. CISA rates the technical impact as partial, and the CVSS data shows no impact on integrity or availability.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.