CVE-2024-5971: Undertow: response write hangs in case of java 17 tlsv1.3 newsessionticket

Published Jun 13, 2024
·
Updated

A vulnerability was found in Undertow, where the chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response. This results in uncontrolled resource consumption, leaving the server side to a denial of service attack. This happens only with Java 17 TLSv1.3 scenarios.

Other sources

A vulnerability was found in Undertow, where the chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response. This results in uncontrolled resource consumption, leaving the server side to a denial of service attack. This happens only with Java 17 TLSv1.3 scenarios.

— NVD

A vulnerability was found in Undertow. Undertow chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response. This results in an uncontrolled resource consumption leaving the server side to a Denial of Service vulnerability attack. This happens only with Java 17 TLSv1.3 scenarios.

— Red Hat

Affected Software

4 affected componentsFixes available
maven/io.undertow:undertow-core<2.2.34.Final
2.2.34.Final
maven/io.undertow:undertow-core>=2.3.0.Alpha1<2.3.15.Final
2.3.15.Final
debian/undertow<2.3.18-1
2.3.18-1
debian/undertow
2.3.20-1

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.2.34.Final
  2. Upgrade

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

    Fixed in 2.3.15.Final
  3. Upgrade

    Upgrade debian/undertow to a version that resolves this vulnerability.

    Fixed in 2.3.18-1
  4. Upgrade

    Upgrade debian/undertow to a version that resolves this vulnerability.

    Fixed in 2.3.20-1

Event History

Jun 13, 2024
Data Sourced
via Red Hat·01:56 PM
DescriptionSeverityAffected Software
Jul 8, 2024
CVE Published
via MITRE·08:51 PM
Data Sourced
via MITRE·08:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-5971?

CVE-2024-5971 is considered a moderate severity vulnerability that can lead to indefinite hanging of client responses.

2

How do I fix CVE-2024-5971?

To fix CVE-2024-5971, upgrade Undertow to version 2.2.34.Final or to 2.3.15.Final.

3

What systems are affected by CVE-2024-5971?

CVE-2024-5971 affects Undertow versions prior to 2.2.34.Final and those in the range from 2.3.0.Alpha1 to 2.3.15.Final.

4

What are the implications of CVE-2024-5971 for my application?

CVE-2024-5971 can cause client applications to hang indefinitely while waiting for responses from the server.

5

Is CVE-2024-5971 being actively exploited?

As of now, there is no public information indicating that CVE-2024-5971 is being actively exploited in the wild.

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