HTTP/2 rapid reset can cause excessive work in net/http
High severity
GitHub Reviewed
Published
Oct 11, 2023
to the GitHub Advisory Database
•
Updated Apr 28, 2024
Description
Published to the GitHub Advisory Database
Oct 11, 2023
Reviewed
Oct 11, 2023
Published by the National Vulnerability Database
Oct 11, 2023
Last updated
Apr 28, 2024
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.
References