Response Splitting from unsanitized headers in http4s
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 8.7epss 1.2%
probabilidad de explotación
1.2%top 34% de las CVE
explotación observada
noninguna fuente lo reporta
http4s is an open source scala interface for HTTP. In affected versions http4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields: Header names (`Header.name`å), Header values (`Header.value`), Status reason phrases (`Status.reason`), URI paths (`Uri.Path`), URI authority registered names (`URI.RegName`) (through 0.21). This issue has been resolved in versions 0.21.30, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following. As a matter of practice http4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend. The carriage return, newline, and null characters are the most threatening.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
Productos afectados
http4s · http4sReferencias
https://github.com/http4s/http4s/commit/d02007db1da4f8f3df2dbf11f1db9ac7afc3f9d8https://github.com/http4s/http4s/security/advisories/GHSA-5vcm-3xc3-w7x3https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#fields.valueshttps://owasp.org/www-community/attacks/HTTP_Response_Splitting