CVE-2024-23644 is a medium-severity (CVSS 6.8) CWE-113 vulnerability in trillium-http. A fix is available for trillium-http — see the affected versions and patch details below.
trillium-http and trillium-client vulnerable to HTTP Request/Response Splitting
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
trillium-http🦀trillium-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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 requests from the client or responses from the server. Thus, if an attacker has sufficient control over header values (or names) in a request or 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.
trillium-client >= 0.5.4:
- If any header name or header value is invalid in the client request headers, awaiting the client Conn returns an
Error::MalformedHeaderprior to any network access.
Workarounds
trillium services and client applications 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.
A note on timing from @jbr on behalf of trillium-rs
@divergentdave filed this vulnerability many months ago but I did not see it until the evening of Jan 23, 2024. Patches were issued less than 24h after reading the vulnerability. The security policy has been updated to avoid delays like this in the future.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | trillium-http | all versions | 0.3.12cargo update -p trillium-http --precise 0.3.12 |
| 🦀crates.io | trillium-client | all versions | 0.5.4cargo update -p trillium-client --precise 0.5.4 |
Affected Products
trilliumtrilliumtrillium-httptrilliumDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trillium-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update trillium-http to 0.3.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23644 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2024-23644 in your dependencies?
Find it across crates.io, including transitive dependencies.