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

Published Aug 16, 2024
·
Updated

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.

Other sources

A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This 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.

Red Hat

Affected Software

12 affected componentsFixes available
maven/io.undertow:undertow-core>=2.3.0.Alpha1<2.3.17.Final
2.3.17.Final
maven/io.undertow:undertow-core<2.2.36.Final
2.2.36.Final
redhat Build Of Apache Camel - Hawtio
redhat Build Of Apache Camel For Spring Boot
redhat Build Of Keycloak
redhat Data Grid=8.0.0
redhat Integration Camel K
redhat JBoss Enterprise Application Platform=7.0.0
redhat JBoss Enterprise Application Platform=8.0.0
redhat Jboss Fuse=7.0.0
redhat Process Automation=7.0
redhat Single Sign-on=7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.undertow:undertow-core to a version that resolves this vulnerability.

    Fixed in 2.3.17.Final
  2. Upgrade

    Upgrade maven/io.undertow:undertow-core to a version that resolves this vulnerability.

    Fixed in 2.2.36.Final

Event History

Aug 16, 2024
Data Sourced
via Red Hat·09:09 AM
DescriptionSeverityAffected Software
Aug 21, 2024
CVE Published
via MITRE·02:13 PM
Data Sourced
via MITRE·02:13 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·03:30 PM
Jul 4, 56726
Event
via FIRST·01:17 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-7885?

The severity of CVE-2024-7885 is classified as high due to potential information disclosure risks.

2

How do I fix CVE-2024-7885?

To fix CVE-2024-7885, upgrade to Undertow version 2.3.17.Final or 2.2.36.Final.

3

Which versions are affected by CVE-2024-7885?

CVE-2024-7885 affects Undertow versions from 2.3.0.Alpha1 up to 2.3.17.Final, and any versions prior to 2.2.36.Final.

4

What type of vulnerability is CVE-2024-7885?

CVE-2024-7885 is a vulnerability related to improper handling of input due to the reuse of a StringBuilder instance.

5

What software packages are impacted by CVE-2024-7885?

CVE-2024-7885 impacts various Red Hat software packages including JBoss, Data Grid, and Keycloak.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203