trillium-http
Affected
- introduced
0.0.0-0, fixed0.3.12(semver)
Fixed versions
0.3.12
Fix
- Fixed version
0.3.12cargo update -p trillium-http --precise 0.3.12
Advisory
Also known as: CVE-2024-23644, GHSA-9f9p-cp3c-72jf, RUSTSEC-2024-0008
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
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:
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
Not rated by the source.
0.0.0-0, fixed 0.3.12 (semver)0.3.12
0.3.12cargo update -p trillium-http --precise 0.3.12Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0