Http4s
Http4s Ember HTTP/2: unbounded continuation frame accumulation
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, When Ember receives an HTTP/2 HEADERS or PUSH_PROMISE frame without END_HEADERS, H2Connection buffers the header block and subsequent CONTINUATION fragments without a size bound. A remote peer can keep an incomplete block open and exhaust heap memory before request decoding, affecting an ember-server or ember-client configured with withHttp2. The remediation tracks accumulated size against SETTINGS_MAX_HEADER_LIST_SIZE derived from EmberServerBuilder.maxHeaderSize or EmberClientBuilder.maxResponseHeaderSize, sends GOAWAY when the limit is exceeded, and applies receiveHeadersTimeout to incomplete blocks. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.23.35
- >= 1.0.0-M1, < 1.0.0-M47
Fixed in 0.23.35, 1.0.0-M47
Mitigation
Upgrade http4s to 0.23.35 or 1.0.0-M47 or later.
References
- Vendor advisory github.com/http4s/http4s/security/advisories/G…
- Patch github.com/http4s/http4s/commit/6e8eccd64a6a74…
- Patch github.com/http4s/http4s/commit/f9dcca4f5a1799…
2 more
- Release notes github.com/http4s/http4s/releases/tag/v0.23.35
- 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.