Connection leaking on idle timeout when TCP congested
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
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
| Plattform | Paket | Anfällige Versionen | Behoben in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.eclipse.jetty.http2:http2-common | >= 9.3.0, < 9.4.54, >= 10.0.0, < 10.0.20, >= 11.0.0, < 11.0.20 | 9.4.54, 10.0.20, 11.0.20 |
| Java / Kotlin (Maven) | org.eclipse.jetty.http2:jetty-http2-common | >= 12.0.0, < 12.0.6 | 12.0.6 |
| Java / Kotlin (Maven) | org.eclipse.jetty.http3:http3-common | >= 10.0.8, < 10.0.20, >= 11.0.8, < 11.0.20 | 10.0.20, 11.0.20 |
| Java / Kotlin (Maven) | org.eclipse.jetty.http3:jetty-http3-common | >= 12.0.0, < 12.0.6 | 12.0.6 |
Verweise
- https://github.com/jetty/jetty.project/security/advisories/GHSA-rggv-cv7r-mw98
- https://nvd.nist.gov/vuln/detail/CVE-2024-22201
- https://github.com/jetty/jetty.project/issues/11256
- https://github.com/jetty/jetty.project/issues/11259
- https://github.com/jetty/jetty.project/commit/0839a208cdc3fcfe25206a77af59ba9fda260188
- https://github.com/jetty/jetty.project/commit/b953871c9a5ff4fbca4a2499848f75182dbd9810
- https://github.com/jetty/jetty.project
- https://lists.debian.org/debian-lts-announce/2024/04/msg00002.html
- https://security.netapp.com/advisory/ntap-20240329-0001
- http://www.openwall.com/lists/oss-security/2024/03/20/2
- CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Schwäche (CWE)
CWE-400, CWE-770- Plattform
- Java / Kotlin (Maven)
- Paket
org.eclipse.jetty.http2:http2-common, org.eclipse.jetty.http2:jetty-http2-common, org.eclipse.jetty.http3:http3-common- Veröffentlicht
- 26.02.2024
- Aktualisiert
- 11.10.2026 13:20
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-rggv-cv7r-mw98 - CC BY 4.0
Schwachstellenhistorie: org.eclipse.jetty.http2:jetty-http2-common
Alle veröffentlichten Schwachstellen dieses Pakets (Java / Kotlin (Maven)), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
- Einträge insgesamt
- 4
- Erste → letzte
- 10.2023 08.2025
- Ohne Fix
- 0
- In Angriffen ausgenutzt
- 1
Verteilung nach Schweregrad
- Hoch 3
- Mittel 1
Veröffentlichungen pro Jahr
- 2023: 1
- 2024: 1
- 2025: 2
- 2026: 0
-
Connection leaking on idle timeout when TCP congested dieser Eintrag
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.