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

New issue

Closed

opened 2023-10-17 17:08:05 +01:00 by Vylpes · 0 comments

Vylpes commented

2023-10-17 17:08:05 +01:00

Owner

Package: undici (npm)
Affected versions: < 5.26.2
Patched version: 5.26.2

Undici clears Authorization headers on cross-origin redirects, but does 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 specification, 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 3rd-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the 3rd party site.

Package: undici (npm) Affected versions: < 5.26.2 Patched version: 5.26.2 --- Undici clears Authorization headers on cross-origin redirects, but does 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 specification, 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 3rd-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the 3rd party site.