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.
CPE | Name | Operator | Version |
---|---|---|---|
golang.org/x/net | lt | 0.23.0 | |
net/http | lt | 1.22.2 | |
golang.org/x/net/http2 | lt | 0.23.0 | |
net/http | lt | 1.21.9 |
www.openwall.com/lists/oss-security/2024/04/03/16
www.openwall.com/lists/oss-security/2024/04/05/4
github.com/advisories/GHSA-4v7x-pqxf-cx7m
go.dev/cl/576155
go.dev/issue/65051
groups.google.com/g/golang-announce/c/YgW0sx8mN3M
lists.fedoraproject.org/archives/list/[email protected]/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT
nowotarski.info/http2-continuation-flood-technical-details
nvd.nist.gov/vuln/detail/CVE-2023-45288
pkg.go.dev/vuln/GO-2024-2687
security.netapp.com/advisory/ntap-20240419-0009