dbcve.org
Cloud FoundationApplication · VMware

CVE-2022-22982

HIGH · 7.5 CVSS v3.1 Published 2022-07-13
Fix available
A fix is available. Upgrade to after 4.3.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 server-side request forgery (SSRF) vulnerability. A malicious actor with network access to 443 on the vCenter Server may exploit this issue by accessing a URL request outside of vCenter Server or accessing an internal service.

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 · high confidence

VMware vCenter Server contains a server-side request forgery (SSRF) vulnerability allowing a remote attacker with network access to port 443 to make the vCenter Server initiate requests to arbitrary external URLs or internal services, potentially exposing internal infrastructure and bypassing network boundaries.

MitigationApply the vendor patch from VMware immediately. Restrict network access to vCenter Server port 443 to trusted sources and implement network segmentation to limit exposure of internal services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.11>= 4.0, <= 4.3.1
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
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if vCenter Server or Cloud Foundation is installed
    Check the system for VMware vCenter Server or VMware Cloud Foundation by reviewing installed software, checking the web management interface login page, or querying the system for VMware-specific processes and services
    Affected if The system runs VMware vCenter Server or VMware Cloud Foundation
  2. Determine the installed version
    Access the vSphere Client or Platform Services Controller admin interface and navigate to 'About' to view the exact version number, or run 'vpxd -v' from the command line if you have shell access
    Affected if The version matches 6.5, 6.7, 7.0 for vCenter Server, or 3.0-3.11 or 4.0-4.3.1 for Cloud Foundation
  3. Verify network exposure of port 443
    Scan the external-facing network interfaces to determine if port 443 is accessible from untrusted networks, or review firewall rules and network security groups for inbound access to port 443
    Affected if Port 443 is exposed to untrusted or internet-facing networks without proper access controls
  4. Check for suspicious outbound connections
    Review vCenter Server logs and network traffic logs for unexpected outbound HTTP/HTTPS requests to unfamiliar external IP addresses or internal infrastructure, particularly from the vCenter Server itself
    Affected if Outbound requests are being made to arbitrary external URLs or internal services that were not initiated by legitimate administrative actions

The environment is affected if vCenter Server version 6.5, 6.7, or 7.0, or Cloud Foundation versions 3.0-3.11 or 4.0-4.3.1 is running with port 443 accessible to untrusted network segments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 a release after 4.3.1
Interim mitigation

Apply the vendor patch from VMware immediately. Restrict network access to vCenter Server port 443 to trusted sources and implement network segmentation to limit exposure of internal services.

Recommended fix High confidence

vCenter Server 6.5 U3t+ / 6.7 U3p+ / 7.0 U3o+; Cloud Foundation 3.11.2+ / 4.3.2+

  1. Identify your current vCenter Server or Cloud Foundation version using the vSphere Client or the 'vmdird' command
  2. Download the appropriate VMware vCenter Server update from my.vmware.com (for version 6.5, 6.7, or 7.0)
  3. Backup the vCenter Server Appliance before applying any updates
  4. Schedule a maintenance window as the update requires a reboot
  5. Upload the update bundle to the vCenter Server via the Update Planner in the vSphere Client
  6. Apply the update: for vCenter Server 6.5, apply 6.5 U3t or later; for 6.7, apply 6.7 U3p or later; for 7.0, apply 7.0 U3o or later
  7. For Cloud Foundation: if on 3.x, upgrade to 3.11.2 or later; if on 4.x, upgrade to 4.3.2 or later
  8. Verify the upgrade was successful by checking the vCenter Server build number matches the expected fixed version
Caveat Ensure compatibility with your ESXi hosts and any dependent solutions before upgrading; some legacy integrations may require updates

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

Fix this in Cloud Foundation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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