Go standard library net/http
HTTP/2 server memory exhaustion due to Trailer headers in net/http
When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.26.9
Fixed in 1.26.9
- >= 1.27.0-0, < 1.27.2
Fixed in 1.27.2
- < 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.