CVE-2024-23644 trillium-http and trillium-client vulnerable to HTTP Request/Response Splitting

Medium 6.8 Published Updated

Attackers can inject CRLF sequences into HTTP headers to split requests or responses, potentially leading to data exfiltration or SSRF.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2024-23644?

CVE-2024-23644 is a medium-severity vulnerability in trillium-rs trillium, published on 24 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Trillium is a composable toolkit for building internet applications with async rust. In `trillium-http` prior to 0.3.12 and `trillium-client` prior to 0.5.4, insufficient validation of outbound header values may lead to request splitting or response splitting attacks in scenarios where attackers have sufficient control over headers. This only affects use cases where attackers have control of request headers, and can insert "\r\n" sequences. Specifically, if untrusted and unvalidated input is inserted into header names or values.

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.)

In `trillium-http` versions 0.3.12 and later, if a header name is invalid in server response headers, the specific header and any associated values are omitted from network transmission. Additionally, 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. In `trillium-client` versions 0.5.4 and later, if any header name or header value is invalid in the client request headers, awaiting the client Conn returns an `Error::MalformedHeader` prior to any network access. As a workaround, 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.

Weakness: CWE-436, CWE-113

Which versions are affected by CVE-2024-23644?

6 open source packages ship an affected version, including trillium-client and trillium-http. It affects 2 products.

PackageAffectedFixed in
trillium-client crates.ioAll versions0.5.4
trillium-client crates.ioAll versions0.5.4
trillium-client crates.ioFrom 0.0.0-00.5.4
trillium-http crates.ioAll versions0.3.12
trillium-http crates.ioAll versions0.3.12
trillium-http crates.ioFrom 0.0.0-00.3.12

Products include Trillium Trillium, Trillium Trillium-Http.

How do I fix CVE-2024-23644?

Upgrade trillium-client to 0.5.4 or later.

Is CVE-2024-23644 being exploited?

There is no known exploitation of CVE-2024-23644 in the wild and no public exploit code.

Sources

Also known as GHSA-9f9p-cp3c-72jf, RUSTSEC-2024-0008, RUSTSEC-2024-0009.

Is CVE-2024-23644 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free