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
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| 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 |
Referencias
- 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
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-400, CWE-770- Plataforma
- Java / Kotlin (Maven)
- Paquete
org.eclipse.jetty.http2:http2-common, org.eclipse.jetty.http2:jetty-http2-common, org.eclipse.jetty.http3:http3-common- Publicada
- 26.02.2024
- Actualizado
- 11.10.2026 13:20
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-rggv-cv7r-mw98 - CC BY 4.0
Historial de vulnerabilidades: org.eclipse.jetty.http2:http2-common
Todas las vulnerabilidades publicadas de este paquete (Java / Kotlin (Maven)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 3
- Primera → última
- 10.2023 08.2025
- Sin corrección
- 0
- Explotada en ataques
- 1
Distribución por gravedad
- Alta 2
- Media 1
Divulgaciones por año
- 2023: 1
- 2024: 1
- 2025: 1
- 2026: 0
-
Connection leaking on idle timeout when TCP congested esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.