| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| org.eclipse.jetty.http2:http2-common | ≥ 10.0.0, < 10.0.20≥ 11.0.0, < 11.0.20≥ 9.3.0, < 9.4.54 | 10.0.2011.0.209.4.54 |
| org.eclipse.jetty.http2:jetty-http2-common | ≥ 12.0.0, < 12.0.6 | 12.0.6 |
| org.eclipse.jetty.http3:http3-common | ≥ 10.0.8, < 10.0.20≥ 11.0.8, < 11.0.20 | 10.0.2011.0.20 |
| org.eclipse.jetty.http3:jetty-http3-common | ≥ 12.0.0, < 12.0.6 | 12.0.6 |
| jetty | ≥ 10.0.0, < 10.0.20≥ 11.0.0, < 11.0.20≥ 12.0.0, < 12.0.6≥ 9.3.0, < 9.4.54 | 10.0.2011.0.2012.0.69.4.54 |
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.
Patched versions:
Disable HTTP/2 and HTTP/3 support until you can upgrade to a patched version of Jetty. HTTP/1.x is not affected.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン