Go standard library net/http
HTTP/2 transport accepts malformed framing-related headers in net/http
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CISA ADP · CWE-444
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Go standard library net/http
- < 1.26.9
Fixed in 1.26.9
Go standard library net/http/internal/http2
- >= 1.27.0-0, < 1.27.2
Fixed in 1.27.2
golang.org/x/net golang.org/x/net/http2
- < 0.60.0
Fixed in 0.60.0
Mitigation
Upgrade net/http to 1.26.9 or later.
Upgrade net/http/internal/http2 to 1.27.2 or later.
Upgrade golang.org/x/net/http2 to 0.60.0 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.