First published: Wed Oct 11 2023(Updated: )
A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.
Credit: security@golang.org security@golang.org security@golang.org
Affected Software | Affected Version | How to fix |
---|---|---|
Golang Go | >=1.20.0<1.20.10 | |
Golang Go | >=1.21.0<1.21.3 | |
Golang Http2 Go | <0.17.0 | |
Fedoraproject Fedora | =37 | |
Fedoraproject Fedora | =38 | |
Fedoraproject Fedora | =39 | |
Netapp Astra Trident | ||
Netapp Astra Trident Autosupport | ||
go/golang.org/x/net | <0.17.0 | 0.17.0 |
redhat/golang | <1.21.3 | 1.21.3 |
redhat/golang | <1.20.10 | 1.20.10 |
debian/golang-1.15 | <=1.15.15-1~deb11u4 | |
debian/golang-1.19 | <=1.19.8-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2023-39325.
A malicious HTTP/2 client that rapidly creates requests and immediately resets them can cause excessive server resource consumption.
By resetting an in-progress request, the attacker can create a new request.
The affected software is golang.org/x/net version 0.17.0.
You can find more information about this vulnerability at the following references: [GitHub Issue](https://github.com/golang/go/issues/63417), [Code Change 1](https://go.dev/cl/534215), [Code Change 2](https://go.dev/cl/534235).