HTTP/1 client connection desynchronization after CONNECT rejection in net/http
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Go standard library | net/http | unaffected |
|
|||||||||
| Go standard library | net/http/httputil | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Go Standard Library | Net/http |
|
||||||||||||
| Go Standard Library | Net/http/httputil |
|
| Source | ID | Title |
|---|---|---|
Ubuntu USN |
USN-8935-1 | Go vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.604% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-444 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go Standard Library
Go Standard Library net/http Go Standard Library net/http/httputil |
|
| Vendors & Products |
Go Standard Library
Go Standard Library net/http Go Standard Library net/http/httputil |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | HTTP/1 client connection desynchronization after CONNECT rejection in net/http | |
| References |
|