Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

trillium-client

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.8crates.ioPublished

    Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in trillium-http and trillium-client

    CVE-2024-23644 · GHSA-9f9p-cp3c-72jf

    Affected
    • crates.io trillium-client < 0.5.4
    Fixed in
    0.5.4· Vendor fix available
    Issue
    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 trilliumhttp::HeaderValue and trilliumhttp::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…

    Recommended action: Upgrade to 0.5.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →