Excessive memory growth in net/http and golang.org/x/net/http2

Summary

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.

Timeline

1. Dec 8, 2022, 7:03 PM UTCCVE published
2. Feb 13, 2025, 4:33 PM UTCRecord last updated

Affected versions

• net/http

  fixed in 1.18.9; From 1.19.0-0 · fixed in 1.19.4

• golang.org/x/net/http2

  fixed in 0.4.0

• golang.org/x/net/http2Go

  fixed in 0.4.0

• golang.org/x/netGo

  fixed in 0.4.0

• stdlibGo

  fixed in 1.18.9; From 1.19.0-0 · fixed in 1.19.4

References 24