CVE-2024-22201

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.

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.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2024-22201 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.4.54, 10.0.20, 11.0.20, 12.0.6); upgrading removes the vulnerable code path.

Kodem intelligence

Patched versions:

• 9.4.54
• 10.0.20
• 11.0.20
• 12.0.6

1. What is CVE-2024-22201? CVE-2024-22201 is a high-severity uncontrolled resource consumption vulnerability in org.eclipse.jetty.http2:http2-common (maven), affecting versions >= 9.3.0, <= 9.4.53. It is fixed in 9.4.54, 10.0.20, 11.0.20, 12.0.6. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2024-22201? CVE-2024-22201 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-22201?
   • org.eclipse.jetty.http2:http2-common (maven) (versions >= 9.3.0, <= 9.4.53)
   • org.eclipse.jetty.http3:http3-common (maven) (versions >= 10.0.8, <= 10.0.19)
   • org.eclipse.jetty.http2:jetty-http2-common (maven) (versions >= 12.0.0, <= 12.0.5)
   • org.eclipse.jetty.http3:jetty-http3-common (maven) (versions >= 12.0.0, <= 12.0.5)
4. Is there a fix for CVE-2024-22201? Yes. CVE-2024-22201 is fixed in 9.4.54, 10.0.20, 11.0.20, 12.0.6. Upgrade to this version or later.
5. Is CVE-2024-22201 exploitable, and should I be worried? Whether CVE-2024-22201 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-22201 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-22201?
   • Upgrade org.eclipse.jetty.http2:http2-common to 9.4.54 or later
   • Upgrade org.eclipse.jetty.http2:http2-common to 10.0.20 or later
   • Upgrade org.eclipse.jetty.http3:http3-common to 10.0.20 or later
   • Upgrade org.eclipse.jetty.http2:http2-common to 11.0.20 or later
   • Upgrade org.eclipse.jetty.http3:http3-common to 11.0.20 or later
   • Upgrade org.eclipse.jetty.http2:jetty-http2-common to 12.0.6 or later
   • Upgrade org.eclipse.jetty.http3:jetty-http3-common to 12.0.6 or later