RUSTSEC-2024-0009

Dashboard / Vulnerabilities / RUSTSEC-2024-0009

RUSTSEC-2024-0009

Summary: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

Details: ### Summary Insufficient validation of outbound header values may lead to request splitting or response splitting attacks in scenarios where attackers have sufficient control over outbound headers. ### Details Outbound `trillium_http::HeaderValue` and `trillium_http::HeaderName` can be constructed infallibly and were not checked for illegal bytes when sending responses from the server. Thus, if an attacker has sufficient control over header values (or names) in an outbound response that they could inject `\r\n` sequences, they could get the client and server out of sync, and then pivot to gain control over other parts of requests or responses. (i.e. exfiltrating data from other requests, SSRF, etc.) ### Patches #### trillium-http >= 0.3.12: * If a header name is invalid in server response headers, the specific header and any associated values are omitted from network transmission. * If a header value is invalid in server response headers, the individual header value is omitted from network transmission. Other headers values with the same header name will still be sent. ### Workarounds trillium services should sanitize or validate untrusted input that is included in header values and header names. Carriage return, newline, and null characters are not allowed. ### Impact This only affects use cases where attackers have control of outbound headers, and can insert "\r\n" sequences. Specifically, if untrusted and unvalidated input is inserted into header names or values. ### Credit Discovered and reported by [@divergentdave](https://github.com/divergentdave)

References: https://crates.io/crates/trillium-http, https://rustsec.org/advisories/RUSTSEC-2024-0009.html, https://github.com/trillium-rs/trillium/security/advisories/GHSA-9f9p-cp3c-72jf