# CVE-2022-22475: Auth bypass in WebSphere Application Server Liberty

> Authenticated users can spoof identities in IBM WebSphere Application Server Liberty, requiring administrators to upgrade to secure versions.

- **Severity:** Medium 5.0 (`CVSS:3.0/PR:L/C:L/AV:N/I:L/A:L/AC:H/UI:N/S:U/RC:C/E:U/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5vv3-v35r-97ch

## What is CVE-2022-22475?

CVE-2022-22475 is a medium-severity authentication bypass vulnerability in Ibm Websphere Application Server, published on 17 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM WebSphere Application Server Liberty and Open Liberty 17.0.0.3 through 22.0.0.5 are vulnerable to identity spoofing by an authenticated user. IBM X-Force ID: 225603.

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

It affects 2 products.


Products: Ibm Open Liberty, Ibm Websphere Application Server.

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

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

## Is CVE-2022-22475 being exploited?

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

## Other vulnerabilities in Ibm Websphere Application Server

- [CVE-2022-22476](https://insights.sbomify.com/CVE-2022-22476/): Auth bypass in WebSphere Application Server Liberty (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22475 is a medium-severity authentication bypass vulnerability in Ibm Websphere Application Server, published on 17 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22475 in the wild and no public exploit code.

Affected product: Ibm Websphere Application Server. 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-22475/ (Markdown: https://insights.sbomify.com/CVE-2022-22475/index.md)
```

## Sources

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

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