First published: Fri Jan 13 2023(Updated: )
A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.
Credit: security@golang.org security@golang.org security@golang.org
Affected Software | Affected Version | How to fix |
---|---|---|
Golang H2c | <2022-11-04 | |
go/golang.org/x/net | >=0.0.0-20220524220425-1d687d428aca<0.1.1-0.20221104162952-702349b0e862 | 0.1.1-0.20221104162952-702349b0e862 |
redhat/golang.org/x/net 0.1.1-0.20221104162952 | <702349 | 702349 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2022-41721 is a vulnerability that allows for a request smuggling attack when using MaxBytesHandler.
CVE-2022-41721 has a severity level of high.
CVE-2022-41721 occurs when the body of an HTTP request is not fully consumed, allowing an attacker to manipulate the request and potentially carry out a request smuggling attack.
The software affected by CVE-2022-41721 includes golang.org/x/net, golang.org/x/net/http2/h2c, and Golang H2c.
To fix CVE-2022-41721, update your affected software to the recommended version provided by the vendor.