Bug 2269607 (CVE-2024-24549) - CVE-2024-24549 : Apache Tomcat: HTTP/2 header handling DoS
Summary: CVE-2024-24549 : Apache Tomcat: HTTP/2 header handling DoS
Keywords:
Status: NEW
Alias: CVE-2024-24549
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2269611
Blocks: 2270597
TreeView+ depends on / blocked
 
Reported: 2024-03-14 20:59 UTC by Zack Miele
Modified: 2024-04-18 11:48 UTC (History)
6 users (show)

Fixed In Version: Apache Tomcat 11.0.0-M17, Apache Tomcat 10.1.19, Apache Tomcat 9.0.86, Apache Tomcat 8.5.99
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in the Tomcat package due to its handling of HTTP/2 requests. Specifically, when an HTTP/2 request surpasses the predetermined limits for headers configured within the server, the associated HTTP/2 stream isn't reset immediately. Instead, the reset action occurs only after all the headers within the request have been processed. This lapse in resetting the stream exposes the system to potential risks, as it allows malicious actors to exploit the delay in stream reset to carry out various attacks, such as header manipulation or resource exhaustion.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:1318 0 None None None 2024-03-18 11:16:13 UTC
Red Hat Product Errata RHSA-2024:1319 0 None None None 2024-03-18 11:13:52 UTC
Red Hat Product Errata RHSA-2024:1324 0 None None None 2024-03-18 14:53:12 UTC
Red Hat Product Errata RHSA-2024:1325 0 None None None 2024-03-18 14:54:02 UTC

Description Zack Miele 2024-03-14 20:59:53 UTC 
Denial of Service due to improper input validation vulnerability for HTTP/2 requests in Apache Tomcat. When processing an HTTP/2 request, if the request exceeded any of the configured limits for headers, the associated HTTP/2 stream was not reset until after all of the headers had been processed.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98.

Users are recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.

https://lists.apache.org/thread/4c50rmomhbbsdgfjsgwlb51xdwfjdcvg
Comment 1 Zack Miele 2024-03-14 21:32:19 UTC 
Created tomcat tracking bugs for this issue:

Affects: fedora-all [bug 2269611]
Comment 4 errata-xmlrpc 2024-03-18 11:13:51 UTC 
This issue has been addressed in the following products:

  JWS 5.7.8

Via RHSA-2024:1319 https://access.redhat.com/errata/RHSA-2024:1319
Comment 5 errata-xmlrpc 2024-03-18 11:16:12 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 5.7 on RHEL 7
  Red Hat JBoss Web Server 5.7 on RHEL 8
  Red Hat JBoss Web Server 5.7 on RHEL 9

Via RHSA-2024:1318 https://access.redhat.com/errata/RHSA-2024:1318
Comment 6 errata-xmlrpc 2024-03-18 14:53:10 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 6.0 on RHEL 8
  Red Hat JBoss Web Server 6.0 on RHEL 9

Via RHSA-2024:1324 https://access.redhat.com/errata/RHSA-2024:1324
Comment 7 errata-xmlrpc 2024-03-18 14:54:01 UTC 
This issue has been addressed in the following products:

  JWS 6.0.1

Via RHSA-2024:1325 https://access.redhat.com/errata/RHSA-2024:1325
Note You need to log in before you can comment on or make changes to this bug.