CVE-2021-22017: VMware vCenter Server Improper Access Control
VMware vCenter Server · listed in the CISA catalog of actively exploited vulnerabilities since 2022-01-10.
- CVSS v3.1 (CISA ADP)
- 5.3
- medium
- EPSS (exploit probability, 30 days)
- 49%
- higher than 98.9% of all CVEs
- Added to CISA KEV
- 2022-01-10
- US federal due date 2022-01-24
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2021-22017 explained
CVE-2021-22017 is an improper access control flaw in rhttproxy as used in VMware vCenter Server. Improper URI normalization lets an attacker with network access to port 443 bypass the proxy and reach internal endpoints. CISA lists it as known exploited, so affected vCenter Server and VMware Cloud Foundation deployments should be updated.
Impact
An unauthenticated attacker with network access to port 443 on vCenter Server can bypass the reverse proxy and access internal endpoints. No user interaction is needed and attack complexity is low. The CVSS rating shows limited confidentiality impact and no integrity or availability impact. CISA rates the flaw as automatable with partial technical impact, so it can be exploited at scale. Attackers are known to use this vulnerability.
Who is affected
The CVE record describes the affected versions in free text: VMware vCenter Server(6.7 before 6.7 U3o and 6.5 before 6.5 U3q) and VMware Cloud Foundation 3.x before 3.10.2.2. The record's fixed-version list is empty, so it names no fixed version as structured data. Check the VMware advisory to confirm the correct update for each product and branch.
Written with AI from the data on this page and checked against it automatically.
Official description
Rhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization. A malicious actor with network access to port 443 on vCenter Server may exploit this issue to bypass proxy leading to internal endpoints being accessed.
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 Server, VMware Cloud FoundationAffectedFixed in
- VMware vCenter Server(6.7 before 6.7 U3o and 6.5 before 6.5 U3q) and VMware Cloud Foundation 3.x before 3.10.2.2
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| VMware vCenter Server, 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-0020.html
- CISA's deadline for US federal agencies: 2022-01-24 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify all vCenter Server 6.5 and 6.7 instances and VMware Cloud Foundation 3.x deployments in your environment.
- Apply the updates named in the VMware advisory, as CISA's required action directs.
- Restrict network access to port 443 on vCenter Server to trusted management networks only.
- Keep vCenter Server management interfaces off the internet.
- Review vCenter Server logs and systems for signs of unauthorized access to internal endpoints.
The CVE record lists no structured fixed version. Follow the VMware advisory to find the release that resolves this flaw for your branch, and apply it as CISA requires. Until updated, limit access to port 443 on vCenter Server to trusted administrative networks and monitor for suspicious requests.
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-23
Questions about CVE-2021-22017
- Does an attacker need credentials to exploit CVE-2021-22017?
- No. The CVSS data shows no privileges and no user interaction are required. Network access to port 443 on vCenter Server is enough.
- Is this vulnerability exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-01-10, with a US federal due date of 2022-01-24. Known ransomware use is listed as unknown.
- What does CISA require?
- CISA's required action is to apply updates per vendor instructions.
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.