CVE-2025-61785 Deno's --deny-write check does not prevent permission bypass
- Published
- Updated
- Exploit status
- No public exploit known
Description
Deno is a JavaScript, TypeScript, and WebAssembly runtime. In versions prior to 2.5.3 and 2.2.15, Deno.FsFile.prototype.utime and Deno.FsFile.prototype.utimeSync are not limited by the permission model check --deny-write=./. It's possible to change to change the access (atime) and modification (mtime) times on the file stream resource even when the file is opened with read only permission (and write: false) and file write operations are not allowed (the script is executed with --deny-write=./). Similar APIs like Deno.utime and Deno.utimeSync require allow-write permission, however, when a file is opened, even with read only flags and deny-write permission, it's still possible to change the access (atime) and modification (mtime) times, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| crates.io deno(crates.io) | < 2.5.3 | 2.5.3 |
| denoland deno | = >= 2.3.0, < 2.5.3 | No fix listed |
| denoland deno | = < 2.2.15 | No fix listed |
| deno | <= 2.2.15 | No fix listed |
| deno | >= 2.3.0, < 2.5.3 | 2.5.3 |
References
- https://github.com/denoland/deno/security/advisories/GHSA-vg2r-rmgp-cgqj exploit vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/denoland/deno/pull/30872 issue-tracking patch
- https://github.com/denoland/deno/commit/992e998dfe436cdc9325232759af8be92f11739b patch
- github.com product
- https://github.com/denoland/deno/releases/tag/v2.2.15 release-notes
- https://github.com/denoland/deno/releases/tag/v2.5.3 release-notes
- github.com