VMware vCenter Server rhttpproxy URI Normalization Bypass
CVE-2021-22017 is a proxy bypass vulnerability in the rhttpproxy component of VMware vCenter Server caused by improper URI normalization. An attacker with network access to TCP port 443 can exploit the normalization flaw to bypass proxy restrictions and access internal endpoints that should not be externally accessible. The vulnerability has a reported CVSS score of 7.3.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation exposes restricted internal vCenter Server endpoints through the externally reachable reverse proxy, bypassing the intended access boundary. Further impact depends on the functionality and authorization controls of the exposed endpoints; code execution or privilege escalation is not established for this vulnerability alone.
If you can’t patch tonight, do this now.
No vulnerability-specific workaround is listed for CVE-2021-22017. As a risk-reduction measure pending patching, restrict network access to vCenter Server TCP port 443 to trusted administrative systems and management networks. This reduces exposure but does not correct the URI normalization flaw.
Patch, then assume compromise.
Apply the VMware updates addressing CVE-2021-22017 in VMSA-2021-0020. Consult the platform-specific response matrix to determine applicability and the required fixed release. The advisory identifies vCenter Server 7.0 U2c, 6.7 U3o, and 6.5 U3q as patch releases for the relevant vulnerability group. For affected VMware Cloud Foundation deployments, follow the corresponding vendor update guidance.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.