# CVE-2024-6162: Undertow: url-encoded request path information can be broken on ajp-listener

> Concurrent requests on the AJP listener can corrupt URL paths, causing legitimate resources to return 404 errors and resulting in denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jun 2024
- **Updated:** 25 Feb 2026
- **Also known as:** DEBIAN-CVE-2024-6162, GHSA-9442-gm4v-r222, UBUNTU-CVE-2024-6162

## What is CVE-2024-6162?

CVE-2024-6162 is a high-severity vulnerability in Red Hat EAP 8.0.1, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Undertow, where URL-encoded request paths can be mishandled during concurrent requests on the AJP listener. This issue arises because the same buffer is used to decode the paths for multiple requests simultaneously, leading to incorrect path information being processed. As a result, the server may attempt to access the wrong path, causing errors such as "404 Not Found" or other application failures. This flaw can potentially lead to a denial of service, as legitimate resources become inaccessible due to the path mix-up.

Weakness: CWE-488 (Exposure of Data Element to Wrong Session)

## Which versions are affected by CVE-2024-6162?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.undertow:undertow-core` | Maven | All versions | 2.2.33.Final |
| `io.undertow:undertow-core` | Maven | All versions | 2.2.33.Final |
| `io.undertow:undertow-core` | Maven | From 2.3.0.Alpha1 | 2.3.14.Final |
| `io.undertow:undertow-core` | Maven | From 2.3.0.Alpha1 | 2.3.14.Final |

## How do I fix CVE-2024-6162?

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

## Is CVE-2024-6162 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6162 and fix it if it is affected.

What it is: CVE-2024-6162 is a high-severity vulnerability in Red Hat EAP 8.0.1, published on 20 Jun 2024. 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-2024-6162 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.33.Final
- io.undertow:undertow-core (Maven): affected all versions; fixed in 2.2.33.Final
- io.undertow:undertow-core (Maven): affected from 2.3.0.Alpha1; fixed in 2.3.14.Final
- io.undertow:undertow-core (Maven): affected from 2.3.0.Alpha1; fixed in 2.3.14.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-2024-6162/ (Markdown: https://insights.sbomify.com/CVE-2024-6162/index.md)
```

## Sources

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

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