Http4s
Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, An Ember server with HTTP/2 enabled through withHttp2 does not enforce SETTINGS_MAX_CONCURRENT_STREAMS for peer-created streams. One unauthenticated connection can open an unbounded number of streams, each retaining per-stream state until heap exhaustion. The same unchecked allocation is reachable in an ember-client through server-initiated PUSH_PROMISE frames because enablePush is not enforced. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-400
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
http4s http4s
- < 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/4983de1f93f2ca…
- Release notes github.com/http4s/http4s/releases/tag/v0.23.35
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.