HTTP/2 CONTINUATION flood in net/http
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 89%. Fixed in 1.21.9, 1.22.2 and 0.23.0.
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Go standard library | <1.21.9, >=1.22.0-0 <1.22.2 | 1.21.9, 1.22.2 | |
| golang.org/x/net | <0.23.0 | 0.23.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket