Excessive memory growth in net/http and golang.org/x/net/http2
Go standard library net/http · golang.org/x/net/http2
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net/http2 Go |
|
|
| golang.org/x/net Go |
|
|
| stdlib Go |
Go standard library net/http · golang.org/x/net/http2
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net/http2 Go |
|
|
| golang.org/x/net Go |
|
|
| stdlib Go |
< 1.18.9≥ 1.19.0-0 · < 1.19.4
|
An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.
From the CVE record · Go
Go servers accepting HTTP/2 requests can allocate excessive memory for cached client-supplied header keys. A remote client sending very large keys can cause approximately 64 MiB of allocation per open connection; the input does not specify authentication requirements or user interaction.
Check Go servers using stdlib versions before 1.18.9 or from 1.19.0 up to but not including 1.19.4, or golang.org/x/net and golang.org/x/net/http2 versions before 0.4.0.