Http4s
Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE
Http4s is a Scala interface for HTTP services. Prior to 0.23.37 and 1.0.0-M48, Ember’s HTTP/2 read loop parses a frame’s 24-bit declared length but waits to buffer the entire payload before comparing it with SETTINGS_MAX_FRAME_SIZE. An unauthenticated peer can declare a payload near 16 MiB on a connection where Ember advertised 16 KiB and either complete or slowly stream it, causing up to 1024-fold memory amplification per connection before processFrame can reject the frame. The shared H2Connection.readLoop affects withHttp2 servers and clients, while HTTP/2-disabled configurations are unaffected, and the patch rejects oversized frames before buffering their payloads. This issue is fixed in versions 0.23.37 and 1.0.0-M48.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.23.37
- >= 1.0.0-M1, < 1.0.0-M48
Fixed in 0.23.37, 1.0.0-M48
Mitigation
Upgrade http4s to 0.23.37 or 1.0.0-M48 or later.
References
- Vendor advisory github.com/http4s/http4s/security/advisories/G…
- Patch github.com/http4s/http4s/commit/87cf334fa3f608…
- Release notes github.com/http4s/http4s/releases/tag/v0.23.37
1 more
- Release notes github.com/http4s/http4s/releases/tag/v1.0.0-M…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.