Skip to main content
Mallory
MediumExploited in the wildCISA KEVVulnerability

CVE-2021-22017: VMware vCenter Server rhttpproxy URI Normalization Bypass

Published Sep 23, 2021 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS49.2%99th percentile
CISA KEVYesAdded Jan 10, 2022
In the wildActivePer CISA KEV
Vendor
VMware
IdentifiersCVE-2021-22017CWE-20

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
VMwareVmware Vcenter Serverapplication
FAQ

Frequently asked questions

Is CVE-2021-22017 exploited in the wild?
Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 10, 2022.
Is there a public exploit for CVE-2021-22017?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2021-22017.
Is there a patch for CVE-2021-22017?
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.
What products are affected by CVE-2021-22017?
Vmware Vcenter Server.
How severe is CVE-2021-22017?
CVE-2021-22017 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 49.2% (99th percentile) as of Oct 25, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.