# CVE-2022-22972: Auth bypass in VMware Workspace ONE Access, Identity Manager and vRealize Automation

> Attackers with network access can bypass authentication to gain administrative privileges in VMware Workspace ONE and related identity management products.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-ffjg-mw44-7fw8

## What is CVE-2022-22972?

CVE-2022-22972 is a critical authentication bypass vulnerability in Vmware Cloud Foundation, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VMware Workspace ONE Access, Identity Manager and vRealize Automation contain an authentication bypass vulnerability affecting local domain users. A malicious actor with network access to the UI may be able to obtain administrative access without the need to authenticate.

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

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-22972?

No fix has been published for CVE-2022-22972 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22972 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-22972 exists.

Public exploit code:

- https://github.com/horizon3ai/CVE-2022-22972 (github_poc): https://github.com/horizon3ai/CVE-2022-22972
- vmware authentication bypass (github_poc): https://github.com/xk4ng/CVE-2022-22972
- IOC List (github_poc): https://github.com/bengisugun/CVE-2022-22972-
- VMware Workspace ONE Access/Identity Manager/vRealize Automation - Authentication Bypass (nuclei): http/cves/2022/CVE-2022-22972.yaml

## 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-2022-22954](https://insights.sbomify.com/CVE-2022-22954/): VMware Workspace ONE Access and Identity Manager Server-Side Template Injection (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22972 is a critical authentication bypass vulnerability in Vmware Cloud Foundation, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-22972 exists.

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-22972/ (Markdown: https://insights.sbomify.com/CVE-2022-22972/index.md)
```

## Sources

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

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