# CVE-2022-31701: Auth bypass in VMware Workspace ONE Access (Access), VMware Identity Manager (vIDM)

> Attackers can bypass authentication in VMware Workspace ONE Access and Identity Manager, potentially gaining unauthorized access to identity services.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-jp99-g9qj-38pv

## What is CVE-2022-31701?

CVE-2022-31701 is a medium-severity authentication bypass vulnerability in Vmware Cloud Foundation, published on 14 Dec 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 broken authentication vulnerability. VMware has evaluated the severity of this issue to be in the Moderate severity range with a maximum CVSSv3 base score of 5.3.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 3 products.


Products: Vmware Access, Vmware Cloud Foundation, Vmware Identity Manager Connector.

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

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

## Is CVE-2022-31701 being exploited?

There is no known exploitation of CVE-2022-31701 in the wild and no public exploit code.

## Other vulnerabilities in Vmware Cloud Foundation

- [CVE-2022-31700](https://insights.sbomify.com/CVE-2022-31700/): Code injection in VMware Workspace ONE Access (Access), VMware Identity Manager (vIDM) (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31701 is a medium-severity authentication bypass vulnerability in Vmware Cloud Foundation, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31701 in the wild and no public exploit code.

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

## Sources

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

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