CVE-2024-22201
HIGHCVE-2024-22201 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty.http2:http2-common. O3 Security confirms whether CVE-2024-22201 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Jetty connection leaking on idle timeout when TCP congested
Blast Radius
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.54 |
| ☕Maven | org.eclipse.jetty.http2:http2-common | ≥ 10.0.0&&< 10.0.20 | 10.0.20 |
| ☕Maven | org.eclipse.jetty.http3:http3-common | ≥ 10.0.8&&< 10.0.20 | 10.0.20 |
| ☕Maven | org.eclipse.jetty.http2:http2-common | ≥ 11.0.0&&< 11.0.20 | 11.0.20 |
| ☕Maven | org.eclipse.jetty.http3:http3-common | ≥ 11.0.8&&< 11.0.20 | 11.0.20 |
| ☕Maven | org.eclipse.jetty.http2:jetty-http2-common | ≥ 12.0.0&&< 12.0.6 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether CVE-2024-22201 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
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.
Frequently Asked Questions
Is CVE-2024-22201 in your dependencies?
O3 detects CVE-2024-22201 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.