Deno run with --allow-read and --deny-read flags results in allowed
denoland deno
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| deno crates.io |
|
|
| deno_runtime crates.io |
denoland deno
| Product | Affected | Fixed in |
|---|---|---|
| deno crates.io |
|
|
| deno_runtime crates.io |
≥ 0.150.0 · < 0.212.0
|
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Starting in version 1.41.3 and prior to versions 2.1.13, 2.2.13, and 2.3.2, `deno run --allow-read --deny-read main.ts` results in allowed, even though 'deny' should be stronger. The result is the same with all global unary permissions given as `--allow-* --deny-*`. This only affects a nonsensical combination of flags, so there shouldn't be a real impact on the userbase. Users may upgrade to version 2.1.13, 2.2.13, or 2.3.2 to receive a patch.
From the CVE record · GitHub_M
Deno can allow an operation when both a global allow flag and its matching deny flag are supplied, even though deny should take precedence. This affects combinations such as `--allow-read --deny-read`; the input describes no attacker scenario and says the combination is unlikely to have a real-world impact.
Check installations of the crates.io `deno` package at >=1.41.3 <2.1.13, >=2.2.0 <2.2.13, or >=2.3.0 <2.3.2, and `deno_runtime` at >=0.150.0 <0.212.0.