Deno run with --allow-read and --deny-read flags results in allowed
- 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 2.1.13, 2.2.13, 2.3.2, 0.212.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: poc
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- denoland deno
From 1.41.3 · fixed in 2.1.13; From 2.2.0 · fixed in 2.2.13; From 2.3.0 · fixed in 2.3.2
- denocrates.io
From 1.41.3 · fixed in 2.1.13
- denocrates.io
From 2.2.0 · fixed in 2.2.13
- denocrates.io
From 2.3.0 · fixed in 2.3.2
- deno_runtimecrates.io
From 0.150.0 · fixed in 0.212.0