Bandit denial of service via HTTP/2 HPACK header amplification
mtrudel bandit
mtrudel bandit
| Product | Affected | Fixed in |
|---|---|---|
| mtrudel bandit |
| No fix yet |
| mtrudel bandit |
| No fix yet |
Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in the HTTP/2 implementation of mtrudel bandit allows an unauthenticated remote attacker to exhaust server memory via a small HPACK-compressed HEADERS block. The block stores one large cookie value in the HPACK dynamic table and then references it tens of thousands of times with 1-byte indexed fields. In the reporter's run, a 49 KB block made a server with default settings allocate a 183 MB cookie binary before any application code ran, and every concurrent stream can repeat the cost.
Bandit.HTTP2.Connection caps only the compressed block (max_header_block_size), and its check of the decoded list against max_header_list_size never fires because that setting defaults to :infinity. combine_cookie_crumbs/1 in lib/bandit/http2/stream.ex then joins every crumb into one binary.
This issue affects bandit: from 0.3.3 before 1.14.0.
From the CVE record · EEF
Bandit's HTTP/2 implementation can expand a small HPACK-compressed HEADERS block into a large cookie value, exhausting server memory before application code runs. An unauthenticated remote attacker can trigger this by sending a crafted block; no user interaction is required.
Operators running mtrudel bandit versions 0.3.3 through versions before 1.14.0 should check their deployments.