Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
http4s
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-ember-core_2.12 Maven |
|
|
| org.http4s:http4s-ember-core_2.13 Maven |
|
|
http4s
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-ember-core_2.12 Maven |
|
|
| org.http4s:http4s-ember-core_2.13 Maven |
|
|
1.0.0-M47| org.http4s:http4s-ember-core_3 Maven |
|
|
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.
From the CVE record · GitHub_M
Ember servers with HTTP/2 enabled through withHttp2 do not enforce the concurrent-stream limit, allowing one unauthenticated connection to open enough streams to exhaust the heap. Ember clients can also allocate unchecked per-stream state from server-initiated PUSH_PROMISE frames because enablePush is not enforced; no user interaction is described.
Check applications using Maven org.http4s:http4s-ember-core_2.12, _2.13, or _3 below 0.23.35, or _2.13 or _3 from 1.0.0-M1 through versions before 1.0.0-M47.