Vulnerability

CVE-2021-22017

Medium· 5.3KEVCVSS5.3EPSS75%

.rules3/5

VMware vCenter Server Improper Access Control

Rhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization.

Threat signal

74/100

High

Severity

medium

CVSS

5.3

EPSS

75%

Active

KEV

CISA KEV — actively exploited

1601d overdue

AffectedVMware — vCenter Server

Added to KEV

2022-01-10

Federal patch due (BOD 22-01)

2022-01-24

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2021-22017

CISA description: “Rhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization.”

CVSS

v3.1Open in FIRST calculator →

5.3/ 10MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactLowSome data disclosure; attacker doesn't fully control what.
Integrity ImpactNoneNo integrity impact.
Availability ImpactNoneNo availability impact.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

74.8%

probability of exploitation in next 30 days

p99

higher than 99% of all CVEs

3-day trend↑ 0pp

Statistically about to be weaponized — top-tier triage urgency.

Vendor VEX

No VEX statements published for CVE-2021-22017. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAttend

Active exploitation with limited impact — coordinate patching

exploitation: active
automatable: no
impact: partial
mission: support

Lifecycle

2022-01-10Added to CISA KEVransomware: Unknown
2022-01-10Published
2022-01-24Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.