CRLF injection in Proxy-Authorization header built from proxy_auth_fun in hackney
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.9.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Hackney, an Erlang HTTP client library, is affected by this flaw when it handles proxy authentication for HTTP CONNECT requests. If the caller's proxy authentication callback builds its return value from untrusted data, such as the proxy's challenge headers, an attacker can inject extra header lines into the request sent to the proxy, which can alter or split the request.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in hackney_http_connect in benoitc hackney allows HTTP Request Splitting via the value a proxy_auth_fun callback returns. After a 407 response from an HTTP CONNECT proxy, hackney_http_connect:handle_proxy_auth/11 calls the caller's proxy_auth_fun with the status code and the response headers and writes the returned binary into the Proxy-Authorization line of the CONNECT retry without checking it. A CR, LF or NUL byte in that value adds header lines to the request sent to the proxy. The value is attacker-influenced when the callback derives it from untrusted data, for example from the proxy's challenge headers. Other caller-supplied values on the CONNECT path, such as the target host and the request headers, were already checked for control bytes. This issue affects hackney: from 2.0.0 before 4.9.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- hackney
From 2.0.0 · fixed in 4.9.0
- benoitc/hackney
From 5df5a74a2817d5b12880d217db33253ff1fae1b5 · fixed in 5ee7d7d19eba27e774667d472feb1e93a08af7f9