Go standard library net/http
HTTP/1 client connection desynchronization after CONNECT rejection in net/http
When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.26.9
- >= 1.27.0-0, < 1.27.2
Fixed in 1.26.9, 1.27.2
- < 1.26.9
- >= 1.27.0-0, < 1.27.2
Fixed in 1.26.9, 1.27.2
Mitigation
Upgrade net/http to 1.26.9 or 1.27.2 or later.
Upgrade net/http/httputil to 1.26.9 or 1.27.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.