First published: Wed Mar 06 2024(Updated: )
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.
Credit: security@golang.org security@golang.org
Affected Software | Affected Version | How to fix |
---|---|---|
go/golang.org/x/net | <0.23.0 | 0.23.0 |
go/net/http | >=1.22.0-0<1.22.2 | 1.22.2 |
go/golang.org/x/net/http2 | <0.23.0 | 0.23.0 |
go/net/http | <1.21.9 | 1.21.9 |
IBM Planning Analytics Local - IBM Planning Analytics Workspace | <=2.1 | |
IBM Planning Analytics Local - IBM Planning Analytics Workspace | <=2.0 | |
redhat/golang | <1.22.2 | 1.22.2 |
redhat/golang | <1.21.9 | 1.21.9 |
redhat/golang.org/x/net | <0.23.0 | 0.23.0 |
debian/golang-1.15 | <=1.15.15-1~deb11u4 | |
debian/golang-1.19 | <=1.19.8-2 | |
debian/golang-1.22 | 1.22.9-2 | |
debian/golang-golang-x-net | <=1:0.0+git20210119.5f4716e+dfsg-4<=1:0.7.0+dfsg-1 | 1:0.27.0-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.