Http4s: Ember Transfer-Encoding value parsing (TE.CL / TE.0 request smuggling)
http4s
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-ember-core_3 Maven |
|
|
| org.http4s:http4s-ember-core_2.13 Maven |
|
http4s
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-ember-core_3 Maven |
|
|
| org.http4s:http4s-ember-core_2.13 Maven |
|
|
| org.http4s:http4s-ember-core_2.12 Maven |
|
|
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, Ember’s HeaderP.parse uses a case-sensitive substring test for the Transfer-Encoding value and decodes header bytes with the platform default charset. Values such as Chunked are not recognized, values such as notchunked are incorrectly accepted, and Unicode case folding can turn a Kelvin-sign byte sequence into a match when UTF-8 is used. Intermediaries that apply RFC-compliant token and charset rules can therefore disagree with Ember’s Content-Length or zero-length framing, enabling TE.CL or TE.0 request smuggling, access-control bypass, cross-user request hijacking, and cache poisoning on the server path. Response smuggling through an ember-client gateway requires a malicious or compromised upstream. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
From the CVE record · GitHub_M
Ember’s header parser can misinterpret Transfer-Encoding values because it uses a case-sensitive substring test and the platform default charset. When an intermediary applies different framing rules, a network attacker can smuggle requests, potentially bypassing access controls, hijacking cross-user requests, or poisoning caches. Response smuggling through an ember-client gateway requires a malicious or compromised upstream.
Check Maven users of org.http4s:http4s-ember-core_3 and _2.13 on versions below 0.23.35 or from 1.0.0-M1 to before 1.0.0-M47, and users of _2.12 on versions below 0.23.35.