dbcve.org
Cloud FoundationApplication · VMware

CVE-2021-22019

HIGH · 7.5 CVSS v3.1 Published 2021-09-23
Fix available
A fix is available. Upgrade to 3.10.2.2 / 4.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The vCenter Server contains a denial-of-service vulnerability in VAPI (vCenter API) service. A malicious actor with network access to port 5480 on vCenter Server may exploit this issue by sending a specially crafted jsonrpc message to create a denial of service condition.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud FoundationApplication
Affected:>= 3.0, < 3.10.2.2>= 4.0, < 4.3
Vcenter ServerApplication
Affected:= 6.5= 6.7= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.10.2.2 / 4.3 or later
Fixed in 3.10.2.24.3
Vendor patch www.vmware.com →
Recommended fix High confidence

Apply vendor patches for affected versions (6.5.0u3+, 6.7.0u3+, 7.0.0u2+); for Cloud Foundation apply 3.10.2.2+ or 4.3+

  1. Review VMSA-2021-0020 advisory for complete patch information and release notes
  2. Identify your exact vCenter Server build number (6.5.x, 6.7.x, or 7.0.x)
  3. Download the corresponding patch from VMware: for vCenter Server 6.5 apply patch 6.5.0u3 or later, for 6.7 apply patch 6.7.0u3 or later, for 7.0 apply patch 7.0.0u2 or later
  4. Follow VMware documentation to apply the patch using the VAMI (Virtual Appliance Management Interface) or CLI
  5. Verify the VAPI service is running and responding after patch application
  6. As an additional mitigation, restrict network access to port 5480 using firewall rules or network segmentation to limit exposure

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22019 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data