# CVE-2024-7885: Undertow: improper state management in proxy protocol parsing causes information leakage

> Improper state management in Undertow's proxy protocol parsing allows information leakage between requests due to shared StringBuilder instances.

- **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:** 21 Aug 2024
- **Updated:** 8 Oct 2026
- **Also known as:** CLSA-2025-1762992412, DEBIAN-CVE-2024-7885, GHSA-9623-mqmm-5rcf, RHSA-2024:7736, UBUNTU-CVE-2024-7885

## What is CVE-2024-7885?

CVE-2024-7885 is a high-severity vulnerability in Redhat Build of Keycloak, published on 21 Aug 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 the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.undertow:undertow-core` | Maven | All versions | 2.2.36.Final |
| `io.undertow:undertow-core` | Maven | All versions | 2.2.36.Final |
| `io.undertow:undertow-core` | Maven | From 2.3.0.Alpha1 | 2.3.17.Final |
| `io.undertow:undertow-core` | Maven | From 2.3.0.Alpha1 | 2.3.17.Final |
| `eap7-undertow` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.2.33-2.SP2_redhat_00001.1.el7eap |
| `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el7eap |
| `eap7-wildfly-java-jdk11` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el7eap |
| `eap7-wildfly-java-jdk8` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el7eap |
| `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el7eap |
| `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el7eap |
| `eap7-undertow` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:2.2.33-2.SP2_redhat_00001.1.el8eap |
| `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el8eap |
| `eap7-wildfly-java-jdk11` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el8eap |
| `eap7-wildfly-java-jdk17` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el8eap |
| `eap7-wildfly-java-jdk8` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el8eap |
| `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el8eap |
| `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el8eap |
| `eap7-undertow` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:2.2.33-2.SP2_redhat_00001.1.el9eap |
| `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el9eap |
| `eap7-wildfly-java-jdk11` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el9eap |
| `eap7-wildfly-java-jdk17` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el9eap |
| `eap7-wildfly-java-jdk8` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el9eap |
| `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el9eap |
| `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.18-1.GA_redhat_00003.1.el9eap |

Products: Redhat Build of Apache Camel - Hawtio, Redhat Build of Apache Camel for Spring Boot, Redhat Build of Keycloak, Redhat Data Grid, Redhat Integration Camel K, Redhat Jboss Enterprise Application Platform, Redhat Jboss Fuse, Redhat Process Automation, Redhat Single Sign-On.

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

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

## Is CVE-2024-7885 being exploited?

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

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-28367](https://insights.sbomify.com/CVE-2026-28367/): Undertow: undertow: request smuggling via `\r\r\r` as a header block terminator (high 8.7)
- [CVE-2026-28368](https://insights.sbomify.com/CVE-2026-28368/): Undertow: undertow: request smuggling via inconsistent header parsing (high 8.7)
- [CVE-2026-28369](https://insights.sbomify.com/CVE-2026-28369/): Undertow: undertow: request smuggling via malformed http request headers (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7885 is a high-severity vulnerability in Redhat Build of Keycloak, published on 21 Aug 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-7885 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.36.Final
- io.undertow:undertow-core (Maven): affected all versions; fixed in 2.2.36.Final
- io.undertow:undertow-core (Maven): affected from 2.3.0.Alpha1; fixed in 2.3.17.Final
- io.undertow:undertow-core (Maven): affected from 2.3.0.Alpha1; fixed in 2.3.17.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-7885/ (Markdown: https://insights.sbomify.com/CVE-2024-7885/index.md)
```

## Sources

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

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