Improper Neutralization of CRLF Sequences in HTTP Headers Affecting trillium-http package, versions <0.3.12


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.06% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RUST-TRILLIUMHTTP-6186526
  • published24 Jan 2024
  • disclosed23 Jan 2024
  • creditDavid Cook

Introduced: 23 Jan 2024

CVE-2024-23644  (opens in a new tab)
CWE-113  (opens in a new tab)

How to fix?

Upgrade trillium-http to version 0.3.12 or higher.

Overview

Affected versions of this package are vulnerable to Improper Neutralization of CRLF Sequences in HTTP Headers via the outbound trillium_http::HeaderValue and trillium_http::HeaderName components. An attacker can manipulate the client-server synchronization and potentially control parts of requests or responses, leading to data exfiltration or server-side request forgery, by injecting \r\n sequences into header values or names.

Notes:

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

  2. trillium-http:

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.

  1. trillium-client:

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.

References

CVSS Scores

version 3.1