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
Configurations
No configuration.
History
04 Nov 2025, 19:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Information
Published : 2024-04-04 21:15
Updated : 2025-11-04 19:16
NVD link : CVE-2023-45288
Mitre link : CVE-2023-45288
CVE.ORG link : CVE-2023-45288
JSON object : View
Products Affected
No product.
CWE
No CWE.
