GHSA-rggv-cv7r-mw98
HIGHConnection leaking on idle timeout when TCP congested
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.
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
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.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 GHSA-rggv-cv7r-mw98 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 GHSA-rggv-cv7r-mw98 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 GHSA-rggv-cv7r-mw98. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rggv-cv7r-mw98 in your dependencies?
O3 detects GHSA-rggv-cv7r-mw98 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.