Http4s: Ember chunk parser lenience (TE.TE request smuggling)
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, Ember’s chunk decoder trims the chunk-size token and accepts leading plus or minus signs instead of requiring one or more hexadecimal digits followed by the required CRLF. When an intermediary forwards chunked data without re-encoding and interprets malformed chunk boundaries differently, an unauthenticated attacker can create TE.TE request smuggling that bypasses intermediary controls, poisons caches, or hijacks the request queue. The same response-path leniency can enable response smuggling against an ember-client used as a gateway when the upstream is malicious or compromised. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
From the CVE record · GitHub_M
Ember’s chunk decoder accepts malformed chunk-size tokens. An unauthenticated network attacker can exploit differing interpretations of chunk boundaries when an intermediary forwards chunked data without re-encoding, potentially bypassing controls, poisoning caches, or hijacking the request queue. A malicious or compromised upstream can also enable response smuggling against an ember-client used as a gateway; no user interaction is described.
Teams running Maven org.http4s:http4s-ember-core_2.12 below 0.23.35, or http4s-ember-core_2.13 or _3 below 0.23.35 or from 1.0.0-M1 through 1.0.0-M46, should check their deployments.