Cookie Request Header Injection via Unvalidated Encoder in cow_cookie:cookie/1
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.21.0 and c17fd73945ef536cccecc492d286fb6b6d1c3307.
Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in ninenines cowlib allows HTTP request splitting and cookie smuggling via unvalidated cookie name and value fields. cow_cookie:cookie/1 in cowlib builds a client-side Cookie: request header from a list of name-value pairs without validating either field. An attacker who controls the cookie names or values passed to this function can inject ;, ,, CR, LF, or TAB characters into the serialized header. This enables two classes of attack: cookie smuggling within a single header (e.g. injecting ; admin=1 to introduce a phantom cookie that the receiving server treats as authentic) and HTTP request header splitting (injecting CRLF to append arbitrary headers or smuggle a complete second request against a shared upstream proxy). The decoder side (parse_cookie_name/1, parse_cookie_value/1) and setcookie/3 already validate and reject these characters; the encoder alone is missing the check. This issue affects cowlib: from 2.9.0 before 2.21.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ninenines | >=2.9.0 <2.21.0, >=f017f8a0ecbffd5033d9ab49bf180186f7a523a7 <c17fd73945ef536cccecc492d286fb6b6d1c3307 | 2.21.0, c17fd73945ef536cccecc492d286fb6b6d1c3307 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket