Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.23.35, 1.0.0-M47
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- http4s http4s
fixed in 0.23.35; From 1.0.0-M1 · fixed in 1.0.0-M47
- org.http4s:http4s-ember-core_2.12Maven
fixed in 0.23.35
- org.http4s:http4s-ember-core_2.13Maven
fixed in 0.23.35
- org.http4s:http4s-ember-core_3Maven
fixed in 0.23.35
- org.http4s:http4s-ember-core_2.13Maven
From 1.0.0-M1 · fixed in 1.0.0-M47
- org.http4s:http4s-ember-core_3Maven
From 1.0.0-M1 · fixed in 1.0.0-M47