HTTP Response Splitting via Non-VCHAR Bytes in cow_http_struct_hd:escape_string/2
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.16.0, 2.22.0, 4401b858f2229abb3ea115c60924f6c77e5f8aa3 and 2 more.
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in ninenines cowlib allows HTTP response splitting via non-VCHAR bytes in structured-fields string values. cow_http_struct_hd:escape_string/2 in cowlib only escapes \ and ", passing all other bytes through verbatim. This creates an encoder/decoder asymmetry: the matching parser accepts only printable ASCII (0x20–0x7E, excluding " and \), but the encoder emits any byte including CR and LF. An application that builds a structured HTTP header via cow_http_struct_hd:item/1 (or a higher-level wrapper such as cow_http_hd:wt_protocol/1) from attacker-controlled input can have \r\n injected into the serialized header value. Once on the wire, the injected CRLF terminates the current header and any following bytes are interpreted as a new header, enabling HTTP response splitting. This issue affects cowlib: from 2.9.0 before 2.22.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ninenines | cowlib | >=2.9.0 <2.16.0 | 2.16.0 |
| ninenines | >=2.9.0 <2.22.0, >=a8b793db3d6ffe91d62f81baf41b1dab4cd78fb6 <4401b858f2229abb3ea115c60924f6c77e5f8aa3 | 2.22.0, 4401b858f2229abb3ea115c60924f6c77e5f8aa3 | |
| hex: cowboy | <2.16.0 | 2.16.0 | |
| hex: gun | <2.4.0 | 2.4.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket