# CVE-2022-22954: VMware Workspace ONE Access and Identity Manager Server-Side Template Injection

> Remote attackers can execute arbitrary code on VMware Workspace ONE Access and Identity Manager via server-side template injection.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 14 Apr 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-q7xc-35g4-g566

## What is CVE-2022-22954?

CVE-2022-22954 is a critical code injection vulnerability in Vmware Cloud Foundation, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-22954?

It affects 5 products.


Products: Vmware Cloud Foundation, Vmware Identity Manager, Vmware Vrealize Automation, Vmware Vrealize Suite Lifecycle Manager, Vmware Workspace One Access.

## How do I fix CVE-2022-22954?

No fix has been published for CVE-2022-22954 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 May 2022.

## Is CVE-2022-22954 being exploited?

Yes. Attackers have exploited CVE-2022-22954 in the wild since at least 14 Apr 2022, including in ransomware campaigns.

Public exploit code:

- 一款针对Vcenter的综合利用工具，包含目前最主流的CVE-2021-21972、CVE-2021-21985以及CVE-2021-22005、One Access的CVE-2022-22954、CVE-2022-22972/31656以及log4j，提供一键上传webshell，命令执行或者上传公钥使用SSH免密连接 (github_poc): https://github.com/Schira4396/VcenterKiller
- POC for VMWARE CVE-2022-22954 (github_poc): https://github.com/sherlocksecurity/VMware-CVE-2022-22954
- CVE-2022-22954 VMware Workspace ONE Access freemarker SSTI 漏洞 命令执行、批量检测脚本、文件写入 (github_poc): https://github.com/bewhale/CVE-2022-22954
- VMware Workspace ONE Access and Identity Manager RCE via SSTI - Test script for shodan, file or manual.  (github_poc): https://github.com/tunelko/CVE-2022-22954-PoC
- 提供批量扫描URL以及执行命令功能。Workspace ONE Access 模板注入漏洞，可执行任意代码 (github_poc): https://github.com/jax7sec/CVE-2022-22954
- CVE-2022-22954 is a server-side template injection vulnerability in the VMware Workspace ONE Access and Identity Manager (github_poc): https://github.com/Vulnmachines/VMWare_CVE-2022-22954

## Other vulnerabilities in Vmware Cloud Foundation

- [CVE-2024-38812](https://insights.sbomify.com/CVE-2024-38812/): VMware vCenter Server Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-37079](https://insights.sbomify.com/CVE-2024-37079/): Broadcom VMware vCenter Server Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2021-22005](https://insights.sbomify.com/CVE-2021-22005/): VMware vCenter Server File Upload (critical 9.8, exploited in the wild)
- [CVE-2021-21985](https://insights.sbomify.com/CVE-2021-21985/): VMware vCenter Server Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2021-21975](https://insights.sbomify.com/CVE-2021-21975/): VMware Server Side Request Forgery in vRealize Operations Manager API (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22954 and fix it if it is affected.

What it is: CVE-2022-22954 is a critical code injection vulnerability in Vmware Cloud Foundation, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-22954 in the wild since at least 14 Apr 2022, including in ransomware campaigns.

Affected product: Vmware Cloud Foundation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-22954/ (Markdown: https://insights.sbomify.com/CVE-2022-22954/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22954
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22954
- OSV: https://osv.dev/vulnerability/CVE-2022-22954

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-22954/
Summaries are generated and may contain mistakes; the official description above is the record.