dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 5 May 2022. Known ransomware use
Identity ManagerApplication · VMware

CVE-2022-22954

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-11
Fix available
A fix is available. Upgrade to after 8.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit 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
VMware Workspace ONE Access and Identity Manager contain a remote code execution vulnerability due to server-side template injection. A malicious actor with network access can trigger a server-side template injection that 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 · high confidence

VMware Workspace ONE Access and Identity Manager contain a remote code execution vulnerability due to server-side template injection (SSTI). A malicious actor with network access can inject malicious template code that gets interpreted by the server-side template engine, leading to arbitrary command execution with the privileges of the affected service.

MitigationApply the VMware security patch for CVE-2022-22954 immediately. If patches are unavailable, restrict network access to the affected systems and consider deploying WAF rules to detect SSTI attack patterns.

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

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
High
Availability
High

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

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 installed VMware product and version
    Access the product admin console or use the product-specific version check command. For Workspace ONE Access, navigate to the About page in the admin dashboard. For Identity Manager, check the /about endpoint or the installation logs.
    Affected if The installed product matches one of the affected versions: VMware Identity Manager (3.3.3-3.3.6), VMware Workspace ONE Access (20.10.0.0, 20.10.0.1, 21.08.0.0, 21.08.0.1), VMware Vrealize Automation (7.6), VMware Cloud Foundation (4.0-4.3.1), or VMware Vrealize Suite Lifecycle Manager (8.0-8.2).
  2. Verify SAML authentication is enabled
    Check the product configuration for SAML identity provider settings. In Workspace ONE Access and Identity Manager, navigate to the Identity & Access Management > Identity Providers section and confirm SAML is configured as an authentication method.
    Affected if SAML authentication is enabled and the product version is in the affected list.
  3. Confirm the vulnerable endpoint is accessible
    The vulnerability exists in the SAML response processing endpoint. Verify if the /SAAS/API/1.0/RestEndpoints/saml endpoint or similar SAML assertion consumer service URLs are exposed.
    Affected if The SAML endpoint is reachable from the network where the attack would originate.
  4. Check network exposure of management interfaces
    Review firewall rules, load balancer configurations, and access policies to determine if the Workspace ONE Access or Identity Manager management interfaces are exposed to untrusted networks.
    Affected if The management interface with SAML configuration is accessible from the internet or untrusted internal networks.

The environment is affected if the installed VMware product version matches one of the affected versions listed and SAML authentication is enabled with the vulnerable endpoint accessible.

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 8.2
Interim mitigation

Apply the VMware security patch for CVE-2022-22954 immediately. If patches are unavailable, restrict network access to the affected systems and consider deploying WAF rules to detect SSTI attack patterns.

Recommended fix Moderate confidence

Upgrade to the fixed releases listed in VMSA-2022-0011 (Identity Manager 3.3.7, Workspace ONE Access 22.06, vRealize Automation 8.0, Cloud Foundation 4.4, vRealize Suite Lifecycle Manager 8.3).

  1. Obtain the VMware security advisory VMSA-2022-0011 for CVE-2022-22954 and identify the fixed versions for each affected product.
  2. Download the patched release for your installation (e.g., Identity Manager 3.3.7, Workspace ONE Access 22.06, vRealize Automation 8.0, Cloud Foundation 4.4, vRealize Suite Lifecycle Manager 8.3).
  3. Plan the upgrade in a non‑production environment to validate that existing workflows and integrations continue to function correctly.
  4. Execute the upgrade following the official VMware upgrade guide for the specific product (back up the database, run pre‑upgrade checks, apply the update, and verify services).
  5. After the upgrade, confirm the vulnerability is remediated by reviewing the release notes and running a vulnerability scan or validation test.
Caveat Moving from vRealize Automation 7.x to 8.x (and similar major version jumps) may introduce breaking changes in APIs, workflows, and configuration; review the release notes and test thoroughly before production rollout.

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

Fix this in Identity Manager Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,300
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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