Deno improperly handles resizable ArrayBuffer
denoland deno
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Deno crates.io |
|
|
| serde_v8 crates.io |
|
|
| deno_runtime crates.io |
denoland deno
| Product | Affected | Fixed in |
|---|---|---|
| Deno crates.io |
|
|
| serde_v8 crates.io |
|
|
| deno_runtime crates.io |
≥ 0.102.0 · < 0.103.0
|
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 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. The problem has been resolved by disabling resizable ArrayBuffers temporarily in Deno 1.32.1. Deno 1.32.2 will re-enable resizable ArrayBuffers with a proper fix. As a workaround, run with `--v8-flags=--no-harmony-rab-gsab` to disable resizable ArrayBuffers.
From the CVE record · GitHub_M
In Deno 1.32.0, a resizable ArrayBuffer passed to an asynchronous function can cause an out-of-bounds read or write if it is shrunk during the operation. This requires the buffer to be passed and shrunk while the operation is in progress; the input does not specify a network, authentication, or user-interaction requirement. Deno Deploy users are not affected.
Check installations of Deno 1.32.0, crates.io serde_v8 >=0.87.0 <0.88.0, and crates.io deno_runtime >=0.102.0 <0.103.0.