Deno's authorization headers not dropped when redirecting cross-origin
denoland deno
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| deno_fetch crates.io |
|
|
| deno crates.io |
|
|
denoland deno
| Product | Affected | Fixed in |
|---|---|---|
| deno_fetch crates.io |
|
|
| deno crates.io |
|
|
Deno is a JavaScript, TypeScript, and WebAssembly runtime with secure defaults. When you send a request with the Authorization header to one domain, and the response asks to redirect to a different domain, Deno'sfetch() redirect handling creates a follow-up redirect request that keeps the original Authorization header, leaking its content to that second domain. This vulnerability is fixed in 2.1.2.
From the CVE record · GitHub_M
Deno’s fetch() can carry an Authorization header to a different domain when a response redirects there. An attacker controlling the redirect destination can receive the header if a request includes one; no additional user interaction is described.
Check installations of deno_fetch versions >=0.0.1 and <0.204.0, and deno versions <=1.46.3 or >=2.0.0 and <2.1.2.