Http4s
Http4s: Ember accepts Transfer-Encoding combined with Content-Length (CL.TE request smuggling)
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, Ember HTTP/1.1 does not reject messages containing both Transfer-Encoding and Content-Length, so an intermediary and Ember can select different body framing rules. When ember-server is behind a keep-alive intermediary that forwards both headers and frames by Content-Length, an unauthenticated attacker can smuggle a second request, bypass intermediary access controls, poison caches, or cause a victim request to be joined to an attacker-controlled prefix. The shared response parser can also desynchronize an ember-client connection when a malicious or compromised upstream sends both headers. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 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/9feaf8677951a5…
- 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.