CVE-2024-22201 — http2-common
HIGHCVE-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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-22201 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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
Jetty is a Java based web server and servlet engine. An HTTP/2 SSL connection that is established and TCP congested will be leaked when it times out. 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 vulnerability is patched in 9.4.54, 10.0.20, 11.0.20, and 12.0.6.
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 |
Detection & 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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-22201 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-22201. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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…
| 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?
O3 Security finds CVE-2024-22201 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.