Http4s has fatal error parsing User-Agent and Server headers
http4s
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-core_2.13 Maven |
|
|
http4s
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-core_2.13 Maven |
|
|
| org.http4s:http4s-core_2.10 Maven |
| No fix yet |
| org.http4s:http4s-core_2.11 Maven |
| No fix yet |
| org.http4s:http4s-core_2.12 Maven |
|
|
| org.http4s:http4s-core Maven |
| No fix yet |
Http4s is a Scala interface for HTTP services. Starting with version 0.1.0 and prior to versions 0.21.34, 0.22.15, 0.23.17, and 1.0.0-M38, the `User-Agent` and `Server` header parsers are susceptible to a fatal error on certain inputs. In http4s, modeled headers are lazily parsed, so this only applies to services that explicitly request these typed headers. Fixes are released in 0.21.34, 0.22.15, 0.23.17, and 1.0.0-M38. As a workaround, use the weakly typed header interface.
From the CVE record · GitHub_M
The http4s User-Agent and Server header parsers can encounter a fatal error on certain inputs. This affects services that explicitly request these lazily parsed, typed headers; the input does not specify authentication or user-interaction requirements.
Engineers running Maven org.http4s:http4s-core_2.13 or http4s-core_2.12 below the fixed releases, or the listed affected http4s-core_2.10, http4s-core_2.11, and unqualified http4s-core versions, should check their deployments.