# CVE-2022-4492: Undertow client not checking server identity presented by server certificate in https connections

> The Undertow client fails to verify server identity in HTTPS connections, allowing potential man-in-the-middle attacks or SSRF-like behaviors.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** DEBIAN-CVE-2022-4492, GHSA-pfcc-3g6r-8rg8, UBUNTU-CVE-2022-4492

## What is CVE-2022-4492?

CVE-2022-4492 is a high-severity server-side request forgery vulnerability in Redhat Jboss Enterprise Application Platform, published on 23 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.

Weakness: CWE-918 (Server-Side Request Forgery)

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

4 open source packages ship an affected version, including io.undertow:undertow-core. It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.undertow:undertow-core` | Maven | All versions | 2.2.24.Final |
| `io.undertow:undertow-core` | Maven | All versions | 2.2.24.Final |
| `io.undertow:undertow-core` | Maven | From 2.3.0 | 2.3.5.Final |
| `io.undertow:undertow-core` | Maven | From 2.3.0 | 2.3.5.Final |

Products: Redhat Build of Quarkus, Redhat Integration Camel for Spring Boot, Redhat Integration Camel K, Redhat Integration Service Registry, Redhat Jboss Enterprise Application Platform, Redhat Jboss Fuse, Redhat Migration Toolkit for Applications, Redhat Migration Toolkit for Runtimes, Redhat Single Sign-On, Redhat Undertow.

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

Upgrade io.undertow:undertow-core to a fixed version for your release line: 2.2.24.Final or 2.3.5.Final.

## Is CVE-2022-4492 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2023-2974](https://insights.sbomify.com/CVE-2023-2974/): quarkus-core vulnerable to client driven TLS cipher downgrading (medium 6.5)
- [CVE-2023-1664](https://insights.sbomify.com/CVE-2023-1664/): Keycloak Untrusted Certificate Validation vulnerability (medium 6.5)
- [CVE-2021-3914](https://insights.sbomify.com/CVE-2021-3914/): SmallRye Health UI Cross-site Scripting vulnerability (medium 6.1)
- [CVE-2023-6393](https://insights.sbomify.com/CVE-2023-6393/): Quarkus: potential invalid reuse of context when @cacheresult on a uni is used (medium 5.3)
- [CVE-2021-3536](https://insights.sbomify.com/CVE-2021-3536/): Cross-site Scripting in Wildfly (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4492 is a high-severity server-side request forgery vulnerability in Redhat Jboss Enterprise Application Platform, published on 23 Feb 2023. 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-4492 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.undertow:undertow-core (Maven): affected all versions; fixed in 2.2.24.Final
- io.undertow:undertow-core (Maven): affected all versions; fixed in 2.2.24.Final
- io.undertow:undertow-core (Maven): affected from 2.3.0; fixed in 2.3.5.Final
- io.undertow:undertow-core (Maven): affected from 2.3.0; fixed in 2.3.5.Final

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

## Sources

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

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