HTTP/2 transport accepts malformed framing-related headers in net/http
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.27.2, 1.26.9, 0.60.0 and 3 more.
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Go standard library | >=1.27.0-0 <1.27.2, <1.26.9 | 1.27.2, 1.26.9 | |
| golang.org/x/net | <0.60.0 | 0.60.0 | |
| go: golang.org/x/net | <0.60.0 | 0.60.0 | |
| go: stdlib | <1.26.9, >=1.27.0-0 <1.27.2 | 1.26.9, 1.27.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in golang.org/x/net (Go), strongest first
Embed
A live severity badge for an advisory, README or ticket