dbcve.org
Cloud FoundationApplication · VMware

CVE-2022-22957

HIGH · 7.2 CVSS v3.1 Published 2022-04-13
Fix available
A fix is available. Upgrade to 5.0 / 9.0 or later.
See remediation →
78/100
Remediation priority · High
Public exploit Remotely reachable 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
VMware Workspace ONE Access, Identity Manager and vRealize Automation contain two remote code execution vulnerabilities (CVE-2022-22957 & CVE-2022-22958). A malicious actor with administrative access can trigger deserialization of untrusted data through malicious JDBC URI which may result in remote code execution.

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
How this class of weakness works · CWE-502

The application rebuilds objects from attacker-supplied serialized data, and the act of rebuilding can trigger dangerous code paths. In many runtimes this leads straight to remote code execution. The durable fix is to avoid deserializing untrusted input — or to use a strict, type-limited format with integrity checks.

General guidance for the deserialization of untrusted data class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Identity ManagerApplication
Affected:= 3.3.3= 3.3.4= 3.3.5= 3.3.6
Vrealize AutomationApplication
Affected:>= 8.0, < 9.0= 7.6
Vrealize Suite Lifecycle ManagerApplication
Affected:>= 8.0, < 9.0
Workspace One AccessApplication
Affected:= 20.10.0.0= 20.10.0.1= 21.08.0.0= 21.08.0.1

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 5.0 / 9.0 or later
Fixed in 5.09.0
Vendor patch www.vmware.com →
Recommended fix High confidence

Product-specific: Workspace ONE Access 21.08.0.2+, Identity Manager 3.3.7+, vRealize Automation 9.0+, vRealize Suite Lifecycle Manager 9.0+, Cloud Foundation 5.0+

  1. 1. Identify the specific VMware product (Workspace ONE Access, Identity Manager, vRealize Automation, vRealize Suite Lifecycle Manager, or Cloud Foundation) running in your environment
  2. 2. Determine the exact current version from the affected versions list
  3. 3. For Workspace ONE Access: upgrade to version 21.08.0.2 or later
  4. 4. For Identity Manager: upgrade to version 3.3.7 or later
  5. 5. For vRealize Automation: upgrade to version 9.0 or later
  6. 6. For vRealize Suite Lifecycle Manager: upgrade to version 9.0 or later
  7. 7. For Cloud Foundation: upgrade to version 5.0 or later
  8. 8. After upgrade, verify the installation and confirm the vulnerability is remediated by reviewing the VMware security advisory VMSA-2022-0011
Caveat Major version upgrades (especially to 9.0 for vRealize products) may require migration planning and could have compatibility implications with existing integrations

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 $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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