Double flow control refund on HTTP/2 server streams in net/http
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.27.2, 1.26.9, 0.60.0 and 3 more.
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Go standard library | >=1.27.0-0 <1.27.2, <1.26.9 | 1.27.2, 1.26.9 | |
| golang.org/x/net | <0.60.0 | 0.60.0 | |
| go: golang.org/x/net | <0.60.0 | 0.60.0 | |
| go: stdlib | <1.26.9, >=1.27.0-0 <1.27.2 | 1.26.9, 1.27.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in golang.org/x/net (Go), strongest first
Embed
A live severity badge for an advisory, README or ticket