Undici's cookie header not cleared on cross-origin redirect in fetch

Summary

Undici is an HTTP/1.1 client written from scratch for Node.js. Prior to version 5.26.2, Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Cookie` headers. By design, `cookie` headers are forbidden request headers, disallowing them to be set in RequestInit.headers in browser environments. Since undici handles headers more liberally than the spec, there was a disconnect from the assumptions the spec made, and undici's implementation of fetch. As such this may lead to accidental leakage of cookie to a third-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the third party site. This was patched in version 5.26.2. There are no known workarounds.

Timeline

1. Oct 12, 2023, 4:35 PM UTCCVE published
2. Sep 17, 2024, 1:10 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Feb 13, 2025, 5:13 PM UTCRecord last updated

Affected versions

• nodejs undici

  fixed in 5.26.2

• undicinpm

  fixed in 5.26.2

References 11