Email me

Rust advisories / trillium-http

Vulnerability MediumRUSTSEC-2024-0009 · trillium-http

RUSTSEC-2024-0009: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

Short answerA security vulnerability in the trillium-http crate: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'). GitHub rates it Medium. Fixed in 0.3.12: update to a fixed version.

Cratetrillium-http
TypeVulnerability
Affected versionsBefore 0.3.12.
Fixed in0.3.12
SeverityMedium (GitHub rating)
Published2024-01-23
Last changed2026-10-12
Also known asCVE-2024-23644, GHSA-9f9p-cp3c-72jf, RUSTSEC-2024-0008

What to do

  1. See which version you have: cargo tree -i trillium-http (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p trillium-http. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example trillium-http = "0.3.12") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Up next

Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ