dbcve.org
Cloud FoundationApplication · VMware

CVE-2021-22007

MEDIUM · 5.5 CVSS v3.1 Published 2021-09-23
Fix available
A fix is available. Upgrade to 5.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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 local information disclosure vulnerability in the Analytics service. An authenticated user with non-administrative privilege may exploit this issue to gain access to sensitive information.

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, < 5.0
Vcenter ServerApplication
Affected:= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 5.0 or later
Fixed in 5.0
Vendor patch www.vmware.com →
Recommended fix Moderate confidence

vCenter Server 6.7 U3o+ / vCenter Server 7.0 U3f+ / Cloud Foundation 5.0+

  1. 1. Determine the current vCenter Server or Cloud Foundation version by logging into the vSphere Client and navigating to the Summary tab, or by running 'vpxd -v' from the vCenter Server Appliance command line
  2. 2. Identify the target fixed version based on your current deployment: For vCenter Server 6.7, upgrade to version 6.7 U3o or later; For vCenter Server 7.0, upgrade to version 7.0 U3f or later; For Cloud Foundation, upgrade to version 5.0 or later
  3. 3. Download the appropriate ISO image from the VMware Customer Connect portal (https://customerconnect.vmware.com) for your target version
  4. 4. Before upgrading, take a complete backup of the vCenter Server Appliance and verify its integrity
  5. 5. Schedule a maintenance window as upgrades require downtime
  6. 6. Mount the ISO image to the vCenter Server Appliance and initiate the upgrade via the interactive installer or use the command line: ./vcsa-ui-installer/lin64/installer
  7. 7. Follow the upgrade wizard, selecting the appropriate deployment type (embedded or external PSC)
  8. 8. After upgrade completes, verify the new version by checking 'About' in the vSphere Client
Caveat vCenter Server upgrades may require downtime; ensure proper backups and test in non-production environment first; some legacy plugins or integrations may require updates for compatibility with newer versions

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,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22007 — 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-22007 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