CVE-2024-22201: Jetty 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 https://github.com/jetty/jetty.project/issues/11256.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.eclipse.jetty.http3:jetty-http3-commonto a version that resolves this vulnerability.Fixed in 12.0.6 - Upgrade
Upgrade
maven/org.eclipse.jetty.http2:jetty-http2-commonto a version that resolves this vulnerability.Fixed in 12.0.6 - Upgrade
Upgrade
maven/org.eclipse.jetty.http3:http3-commonto a version that resolves this vulnerability.Fixed in 11.0.20 - Upgrade
Upgrade
maven/org.eclipse.jetty.http2:http2-commonto a version that resolves this vulnerability.Fixed in 11.0.20 - Upgrade
Upgrade
maven/org.eclipse.jetty.http3:http3-commonto a version that resolves this vulnerability.Fixed in 10.0.20 - Upgrade
Upgrade
maven/org.eclipse.jetty.http2:http2-commonto a version that resolves this vulnerability.Fixed in 10.0.20 - Upgrade
Upgrade
maven/org.eclipse.jetty.http2:http2-commonto a version that resolves this vulnerability.Fixed in 9.4.54 - Upgrade
Upgrade
jettyto a version that resolves this vulnerability.Fixed in 9.4.54 - Upgrade
Upgrade
jettyto a version that resolves this vulnerability.Fixed in 10.0.20 - Upgrade
Upgrade
jettyto a version that resolves this vulnerability.Fixed in 11.0.20 - Upgrade
Upgrade
jettyto a version that resolves this vulnerability.Fixed in 12.0.6 - Configuration
Disable HTTP/2 and HTTP/3 support until you can upgrade to a patched version of Jetty (HTTP/1.x is not affected).
Jetty HTTP/2 and HTTP/3 HTTP/2/HTTP/3 support = disabled
Event History
Frequently Asked Questions
What is the severity of CVE-2024-22201?
CVE-2024-22201 has a moderate severity rating due to its potential impact on HTTP/2 connections during TCP congestion.
How do I fix CVE-2024-22201?
To remediate CVE-2024-22201, upgrade to version 12.0.6 or apply the necessary patches based on your affected software version.
Which versions are affected by CVE-2024-22201?
CVE-2024-22201 affects Jetty HTTP/2 versions 12.0.0 to 12.0.5, 11.0.0 to 11.0.19, 10.0.0 to 10.0.19, and 9.3.0 to 9.4.53.
Is there a workaround for CVE-2024-22201?
There is no specific workaround for CVE-2024-22201; the best practice is to update to the latest patched version of the affected software.
What products are impacted by CVE-2024-22201?
CVE-2024-22201 impacts various Jetty packages as well as IBM Cognos Analytics versions up to 12.0.3 and 11.2.4 FP4.