dbcve.org
Build Of Apache Camel HawtioWeb server / proxy · Redhat

CVE-2024-7885

HIGH · 7.5 CVSS v3.1 Published 2024-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Undertow's ProxyProtocolReadListener contains a StringBuilder reuse vulnerability in the parseProxyProtocolV1 method. When processing multiple HTTP requests on the same connection, the same StringBuilder instance is reused, causing data from previous requests/responses to potentially leak into subsequent requests. This creates a risk of sensitive information exposure between requests on keep-alive connections.

MitigationUpgrade to a patched version of Undertow that creates a new StringBuilder instance for each request in the parseProxyProtocolV1 method, or apply the code-level fix to ensure request isolation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of Apache Camel HawtioWeb server / proxy
Affected:all versions
Build Of Apache Camel For Spring BootWeb server / proxy
Affected:all versions
Build Of KeycloakApplication
Affected:all versions
Data GridApplication
Affected:= 8.0.0
Integration Camel KApplication
Affected:all versions
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0= 8.0.0
Jboss FuseApplication
Affected:= 7.0.0
Process AutomationApplication
Affected:= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Undertow usage in the environment
    Search for undertow-core JAR files in the application deployment, or check for 'org.apache.catalina.connector.Request' (Undertow's Request class) in loaded classes. For JBoss EAP, check the modules directory for undertow-core presence.
    Affected if Undertow is present in the application runtime
  2. Verify ProxyProtocol is enabled
    Check configuration files (standalone.xml for JBoss EAP, undertow-servlet.xml, or web.xml) for the 'proxy-protocol' attribute or <proxy-protocol> element in the undertow subsystem. Search for 'enable-proxy-protocol' or 'undertow:proxy-protocol' in configuration.
    Affected if ProxyProtocol is explicitly enabled in the Undertow server configuration
  3. Confirm HTTP keep-alive is in use
    Review the Undertow configuration for 'connection-pool' settings or 'max-keep-alive-requests'. Check if HTTP keep-alive is not explicitly disabled. Look for 'Connection: keep-alive' handling in the server config.
    Affected if HTTP keep-alive connections are permitted (the default setting)
  4. Check if parseProxyProtocolV1 is being invoked
    Enable Undertow access logging and monitor requests to the server. The vulnerability triggers when ProxyProtocol parses the connection header. Review server logs for proxy protocol related entries.
    Affected if The server accepts proxy protocol connections and processes HTTP requests on the same TCP connection over time

The environment is affected if Undertow is present with ProxyProtocol enabled and HTTP keep-alive connections are in use, allowing data to potentially leak between consecutive requests on the same connection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Undertow that creates a new StringBuilder instance for each request in the parseProxyProtocolV1 method, or apply the code-level fix to ensure request isolation.

Fix this in Build Of Apache Camel Hawtio Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7885 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data