Http4s blaze
blaze: Multiple HTTP/1.1 request-smuggling primitives in blaze's Java wire parser
blaze is a Scala library for building asynchronous pipelines, with a focus on network IO. Prior to 0.23.18 and from 1.0.0-M1 until 1.0.0-M42, five HTTP/1.1 conformance laxities in the hand-written Java parser under http/src/main/java/org/http4s/blaze/http/parser/ can cause blaze to derive a different request boundary than a stricter fronting intermediary. A default BlazeServerBuilder accepts invalid or valueless header field names that violate tchar syntax, obsolete folded field lines (obs-fold), unsupported Transfer-Encoding values, duplicate Content-Length fields, and requests containing both Transfer-Encoding and Content-Length. If a lenient or legacy proxy forwards the malformed bytes but interprets them differently, the disagreement can permit front-end authorization bypass, response-queue poisoning on pooled backend connections, or cache poisoning. Exploitation requires a pair of disagreeing parsers; no non-default blaze configuration is required. The affected checks are enforced in BodyAndHeaderParser and Http1ServerParser. This issue is fixed in versions 0.23.18 and 1.0.0-M42.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.23.18
- >= 1.0.0-M1, < 1.0.0-M42
Fixed in 0.23.18, 1.0.0-M42
- < 0.23.18
- >= 1.0.0-M1, < 1.0.0-M42
Fixed in 0.23.18, 1.0.0-M42
- < 0.23.18
- >= 1.0.0-M1, < 1.0.0-M42
Fixed in 0.23.18, 1.0.0-M42
- < 0.23.18
Fixed in 0.23.18
Mitigation
Upgrade blaze to 0.23.18 or 1.0.0-M42 or later.
Upgrade blaze-http_2.13 to 0.23.18 or 1.0.0-M42 or later.
Upgrade blaze-http_3 to 0.23.18 or 1.0.0-M42 or later.
Upgrade http4s-blaze-server_2.13 to 0.23.18 or later.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.