CVE-2024-34750

Apache Tomcat: HTTP/2 excess header handling DoS

HIGH
7.5
CVSS Score
Published: July 3, 2024 at 07:32 PM UTC
Updated: June 17, 2026 at 07:34 AM UTC
2 products affected across 2 vendorsTomcatOntap Tools

Using Apache Tomcat by Apache Software Foundation?

Get instant alerts when new vulnerabilities affect Apache Tomcat - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 5%
SSVC
No known exploit

Description

Improper Handling of Exceptional Conditions, Uncontrolled Resource Consumption vulnerability in Apache Tomcat. When processing an HTTP/2 stream, Tomcat did not handle some cases of excessive HTTP headers correctly. This led to a miscounting of active HTTP/2 streams which in turn led to the use of an incorrect infinite timeout which allowed connections to remain open which should have been closed. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M20, from 10.1.0-M1 through 10.1.24, from 9.0.0-M1 through 9.0.89. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Users are recommended to upgrade to version 11.0.0-M21, 10.1.25 or 9.0.90, which fixes the issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.1.0 ≤ v < 10.1.2510.1.0-M1 ≤ v ≤ 10.1.2410.1.0-m1 ≤ v ≤ 10.1.2411.0.0-M1 ≤ v ≤ 11.0.0-M2011.0.0-m1 ≤ v ≤ 11.0.0-m208.5.0 ≤ v ≤ 8.5.1009.0.0 ≤ v < 9.0.909.0.0-M1 ≤ v ≤ 9.0.899.0.0-m1 ≤ v ≤ 9.0.8910.1.0-M110.1.0-m111.0.0 milestone111.0.0 milestone1011.0.0 milestone1111.0.0 milestone1211.0.0 milestone1311.0.0 milestone1411.0.0 milestone1511.0.0 milestone1611.0.0 milestone1711.0.0 milestone1811.0.0 milestone1911.0.0 milestone211.0.0 milestone2011.0.0 milestone311.0.0 milestone411.0.0 milestone511.0.0 milestone611.0.0 milestone711.0.0 milestone811.0.0 milestone911.0.0-M111.0.0-m18.5.09.0.0-M19.0.0-m1
Affected range stops below 10.1.25, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.0.90, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 10.0.0-M1 (unknown)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400CWE-755

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card