GHSA-cp4q-fqw9-4hf6: Http4s Ember HTTP/2: unbounded continuation frame accumulation
Source: github.com
When Ember receives an HTTP/2 HEADERS or PUSH_PROMISE frame without the END_HEADERS flag, it buffers the header block fragment and waits for subsequent CONTINUATION frames. These accumulate unbounded until the connection closes. Impact A remote, unauthenticated peer can exhaust the heap on any Ember endpoint that has HTTP/2 enabled: - ember-server with .withHttp2: any HTTP/2 client can trigger this against any reachable path (including paths that return 404). No authentication is required because the attack completes before the request is decoded. …
Signalsas the pipeline stamped them
High High-risk vulnerability — CVSS 7.5
CVEKEV and EPSS where known
Get the next one first
Every story goes to Telegram and RSS the moment it is published, and the whole wire is a keyless JSON API.