CVE-2024-22201 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty.http2:http2-common. A fix is available for org.eclipse.jetty.http2:http2-common — see the affected versions and patch details below.
Jetty connection leaking on idle timeout when TCP congested
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-22201.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.eclipse.jetty.http2:http2-common☕org.eclipse.jetty.http2:http2-common☕org.eclipse.jetty.http3:http3-common☕org.eclipse.jetty.http2:http2-common☕org.eclipse.jetty.http3:http3-common☕org.eclipse.jetty.http2:jetty-http2-common☕org.eclipse.jetty.http3:jetty-http3-commonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
If an HTTP/2 connection gets TCP congested, when an idle timeout occurs the HTTP/2 session is marked as closed, and then a GOAWAY frame is queued to be written. However it is not written because the connection is TCP congested. When another idle timeout period elapses, it is then supposed to hard close the connection, but it delegates to the HTTP/2 session which reports that it has already been closed so it does not attempt to hard close the connection.
This leaves the connection in ESTABLISHED state (i.e. not closed), TCP congested, and idle.
An attacker can cause many connections to end up in this state, and the server may run out of file descriptors, eventually causing the server to stop accepting new connections from valid clients.
The client may also be impacted (if the server does not read causing a TCP congestion), but the issue is more severe for servers.
Patches
Patched versions:
- 9.4.54
- 10.0.20
- 11.0.20
- 12.0.6
Workarounds
Disable HTTP/2 and HTTP/3 support until you can upgrade to a patched version of Jetty. HTTP/1.x is not affected.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty.http2:http2-common | ≥ 9.3.0&&< 9.4.54 | 9.4.54org.eclipse.jetty.http2:http2-common:9.4.54 |
| ☕Maven | org.eclipse.jetty.http2:http2-common | ≥ 10.0.0&&< 10.0.20 | 10.0.20org.eclipse.jetty.http2:http2-common:10.0.20 |
| ☕Maven | org.eclipse.jetty.http3:http3-common | ≥ 10.0.8&&< 10.0.20 | 10.0.20org.eclipse.jetty.http3:http3-common:10.0.20 |
| ☕Maven | org.eclipse.jetty.http2:http2-common | ≥ 11.0.0&&< 11.0.20 | 11.0.20org.eclipse.jetty.http2:http2-common:11.0.20 |
| ☕Maven | org.eclipse.jetty.http3:http3-common | ≥ 11.0.8&&< 11.0.20 | 11.0.20org.eclipse.jetty.http3:http3-common:11.0.20 |
| ☕Maven | org.eclipse.jetty.http2:jetty-http2-common | ≥ 12.0.0&&< 12.0.6 | 12.0.6org.eclipse.jetty.http2:jetty-http2-common:12.0.6 |
Affected Products
debian linuxdebianjettyeclipseactive iq unified managernetappbluexpnetappDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty.http2:http2-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty.http2:http2-common to 9.4.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22201 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The issue in Jetty where HTTP/2 connections can enter a congested, idle state and potentially exhaust server file descriptors represents a moderate severity due to its impact on system resources and service availability. While the vulnerability requires the deliberate creation of numerous congested connections by an…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-22201 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.440.3.1716445200-3.el8 | RHSA-2024:3635 |
| OCP-Tools-4.13-RHEL-8 | jenkins-0:2.440.3.1716445150-3.el8 | RHSA-2024:3636 |
| OCP-Tools-4.14-RHEL-8 | jenkins-0:2.440.3.1716387933-3.el8 | RHSA-2024:3634 |
| OCP-Tools-4.15-RHEL-8 | jenkins-0:2.440.3.1718879390-3.el8 | RHSA-2024:4597 |
| Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2 | jetty | RHSA-2024:4884 |
| Red Hat build of Apicurio Registry 2.6.1 GA | jetty | RHSA-2024:4873 |
Frequently Asked Questions
Is CVE-2024-22201 in your dependencies?
Find it across Maven, including transitive dependencies.