cve/2023/CVE-2023-45288.md

### [CVE-2023-45288](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-45288)
![](https://img.shields.io/static/v1?label=Product&message=golang.org%2Fx%2Fnet%2Fhttp2&color=blue)
![](https://img.shields.io/static/v1?label=Product&message=net%2Fhttp&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=0%3C%200.23.0%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Version&message=0%3C%201.21.9%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-400%3A%20Uncontrolled%20Resource%20Consumption&color=brighgreen)

### Description

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.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/0xCuteSocks/cve-2023-45288
- https://github.com/Ampferl/poc_http2-continuation-flood
- https://github.com/DrewskyDev/H2Flood
- https://github.com/Vos68/HTTP2-Continuation-Flood-PoC
- https://github.com/aerospike-managed-cloud-services/flb-output-gcs
- https://github.com/blackmagic2023/http-2-DOS-PoC
- https://github.com/hex0punk/cont-flood-poc
- https://github.com/mkloubert/go-package-manager
- https://github.com/nics-tw/sbom2vans
- https://github.com/nomi-sec/PoC-in-GitHub
- https://github.com/testing-felickz/docker-scout-demo