NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2023-45288: net/http, x/net/http2: close connections when receiving too many headers

mediumCVSS 3.1 5.3GHSA-4v7x-pqxf-cx7m

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

Published Apr 4, 2024 · Updated Nov 4, 2025

Affected packages

net/http

Ecosystem
Go
Affected
< 1.21.9
Fixed in
1.21.9
Check
go list -m net/http

golang.org/x/net/http2

Ecosystem
Go
Affected
< 0.23.0
Fixed in
0.23.0
Check
go list -m golang.org/x/net/http2

net/http

Ecosystem
Go
Affected
>= 1.22.0-0, < 1.22.2
Fixed in
1.22.2
Check
go list -m net/http

golang.org/x/net

Ecosystem
Go
Affected
< 0.23.0
Fixed in
0.23.0
Check
go list -m golang.org/x/net

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries