| - transferReader.parseTransferEncoding |
| summary: Improper sanitization of Transfer-Encoding headers in net/http |
| The HTTP/1 client accepted some invalid Transfer-Encoding headers as indicating |
| a "chunked" encoding. This could potentially allow for request smuggling, but |
| only if combined with an intermediate server that also improperly failed to |
| reject the header as invalid. |
| published: 2022-07-25T17:34:18Z |
| - Zeyu Zhang (https://www.zeyu2001.com/) |
| - fix: https://go.dev/cl/409874 |
| - fix: https://go.googlesource.com/go/+/e5017a93fcde94f09836200bca55324af037ee5f |
| - report: https://go.dev/issue/53188 |
| - fix: https://go.dev/cl/410714 |
| - web: https://groups.google.com/g/golang-announce/c/nqrv9fbR0zE |
| cwe: 'CWE-444: Inconsistent Interpretation of HTTP Requests (''HTTP Request Smuggling'')' |
| Acceptance of some invalid Transfer-Encoding headers in the HTTP/1 client in |
| net/http before Go 1.17.12 and Go 1.18.4 allows HTTP request smuggling if |
| combined with an intermediate server that also improperly fails to reject the |