Deno improperly handles resizable ArrayBuffer
### Impact [Resizable ArrayBuffers](https://github.com/tc39/proposal-resizablearraybuffer) passed to asynchronous native functions that are shrunk during the asynchronous operation could result in an out-of-bound read/write. It is unlikely that this has been exploited in the wild, as the only version affected is Deno 1.32.0. Deno Deploy users are not affected. ### Patches The problem has been resolved by disabling resizable ArrayBuffers temporarily in Deno 1.32.1. A future version of Deno will re-enable resizable ArrayBuffers with a proper fix. ### Workarounds Upgrade to Deno 1.32.1, or run with `--v8-flags=--no-harmony-rab-gsab` to disable resizable ArrayBuffers.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-28445US | critical9.8 | — | ||
Deno is a runtime for JavaScript and TypeScript that uses V8 and is built in Rust. Resizable ArrayBuffers passed to asynchronous functions that are shrunk during the asynchronous o… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/denoland/denoPACKAGE
- https://github.com/denoland/deno/pull/18395WEB
- https://github.com/denoland/deno/pull/18452WEB
- https://github.com/denoland/deno/releases/tag/v1.32.1WEB
- https://github.com/denoland/deno/security/advisories/GHSA-c25x-cm9x-qqgxWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-28445ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan