Connection leaking on idle timeout when TCP congested

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2024-22201: 1.43% estimated exploitation activity in the next 30 days; percentile 73.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

26 Feb 2024, 20:13 UTC

Last modified by the source

14 Mar 2026, 05:09 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rggv-cv7r-mw98

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-22201

Advisory: Connection leaking on idle timeout when TCP congested
IDs: CVE-2024-22201, GHSA-rggv-cv7r-mw98
Record: https://patchnext.com/advisories/cve-2024-22201 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jetty.http3:jetty-http3-common 12.0.6; org.eclipse.jetty.http2:jetty-http2-common 12.0.6; org.eclipse.jetty.http2:http2-common 11.0.20, 10.0.20, 9.4.54; org.eclipse.jetty.http3:http3-common 11.0.20, 10.0.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jetty.http3:jetty-http3-common: affected >= 12.0.0, <= 12.0.5; fixed in 12.0.6
- Maven org.eclipse.jetty.http2:jetty-http2-common: affected >= 12.0.0, <= 12.0.5; fixed in 12.0.6
- Maven org.eclipse.jetty.http2:http2-common: affected >= 9.3.0, <= 9.4.53; >= 10.0.0, <= 10.0.19; >= 11.0.0, <= 11.0.19; fixed in 10.0.20, 11.0.20, 9.4.54
- Maven org.eclipse.jetty.http3:http3-common: affected >= 10.0.8, <= 10.0.19; >= 11.0.8, <= 11.0.19; fixed in 10.0.20, 11.0.20

## Suggested inspection (read-only)
- Maven org.eclipse.jetty.http3:jetty-http3-common: check the installed version with your package manager.
- Maven org.eclipse.jetty.http2:jetty-http2-common: check the installed version with your package manager.
- Maven org.eclipse.jetty.http2:http2-common: check the installed version with your package manager.
- Maven org.eclipse.jetty.http3:http3-common: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jetty.http3:jetty-http3-common, org.eclipse.jetty.http2:jetty-http2-common, org.eclipse.jetty.http2:http2-common, org.eclipse.jetty.http3:http3-common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rggv-cv7r-mw98 (GitHub-reviewed advisory GHSA-rggv-cv7r-mw98 lists affected ranges: Maven org.eclipse.jetty.http2:http2-common >=9.3.0 =10.0.0 =11.0.0 =10.0.8 =11.0.8 =12.0.0 =12.0.0 <=12.0.5)

Commands are suggestions: review each one before running it.