CVE-2024-34346
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeno is a JavaScript, TypeScript, and WebAssembly runtime with secure defaults. The Deno sandbox may be unexpectedly weakened by allowing file read/write access to privileged files in various locations on Unix and Windows platforms. For example, reading `/proc/self/environ` may provide access equivalent to `--allow-env`, and writing `/proc/self/mem` may provide access equivalent to `--allow-all`. Users who grant read and write access to the entire filesystem may not realize that these access to these files may have additional, unintended consequences. The documentation did not reflect that this practice should be undertaken to increase the strength of the security sandbox. Users who run code with `--allow-read` or `--allow-write` may unexpectedly end up granting additional permissions via file-system operations. Deno 1.43 and above require explicit `--allow-all` access to read or write `/etc`, `/dev` on unix platform (as well as `/proc` and `/sys` on linux platforms), and any path starting with `\\` on Windows.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDeno's sandbox security is weakened when users grant `--allow-read` or `--allow-write` permissions, unexpectedly providing access to privileged system files. On Unix, reading `/proc/self/environ` can expose environment variables equivalent to `--allow-env`, and writing `/proc/self/mem` can provide root-equivalent access. On Linux, `/etc`, `/dev`, `/proc`, and `/sys` contain sensitive system resources. Windows paths starting with `\\` are similarly privileged.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.43.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check your installed Deno versionRun `deno --version` and compare the version number to the affected range (< 1.43.1)Affected if The version is lower than 1.43.1
-
Identify scripts using --allow-read permissionSearch your codebase or deployment scripts for `deno run` commands containing `--allow-read` flag without explicit path restrictionsAffected if Scripts use --allow-read without restricting access to specific directories (e.g., --allow-read=/specific/path)
-
Identify scripts using --allow-write permissionSearch your codebase or deployment scripts for `deno run` commands containing `--allow-write` flag without explicit path restrictionsAffected if Scripts use --allow-write without restricting access to specific directories (e.g., --allow-write=/specific/path)
-
Inspect for access to Unix privileged pathsSearch your Deno scripts for file read or write operations targeting /proc/self/environ, /proc/self/mem, /etc, /dev, /proc, or /sys directoriesAffected if Your code reads from or writes to any of these privileged system directories with --allow-read or --allow-write permissions
-
Inspect for access to Windows privileged pathsSearch your Deno scripts for file operations targeting paths starting with \\ (UNC paths)Affected if Your code accesses UNC paths (\\server\share or \\.) with --allow-read or --allow-write permissions
You are affected if you run Deno version below 1.43.1 and your scripts use --allow-read or --allow-write permissions that could access protected system paths like /proc/self/environ, /proc/self/mem, /etc, /dev, /proc, /sys, or Windows UNC paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.43.1
Upgrade to Deno 1.43 or later, which requires explicit `--allow-all` to access these protected paths. Review existing code that uses `--allow-read` or `--allow-write` to ensure no unintended access to privileged system files occurs.
Deno 1.43.1 or later
- Verify current Deno version by running: deno --version
- Upgrade Deno to version 1.43.1 or later using your preferred installation method
- For fresh installation: curl -fsSL https://deno.land/install.sh | sh
- For existing installations using Deno's built-in updater: deno upgrade
- For npm-based installations: npm install -g deno
- After upgrade, verify the version: deno --version
- Ensure your code explicitly requests --allow-all if access to /etc, /dev, /proc, /sys (Linux) or \\ paths (Windows) is needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-34346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data