A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module…
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 3%. Fixed in 10.*, 11.*, 12.* and 12 more.
A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| nodejs | >=10.0 <10.*, >=11.0 <11.*, >=12.0 <12.*, >=13.0 <13.*, >=14.0 <14.*, >=15.0 <15.*, >=16.0 <16.*, >=17.0 <17.*, >=18.0 <18.*, >=20.19.6 <=20.19.6, >=22.21.1 <=22.21.1, >=24.12.0 <=24.12.0, >=25.2.1 <=25.2.1, >=4.0 <4.*, >=5.0 <5.*, >=6.0 <6.*, >=7.0 <7.*, >=8.0 <8.*, >=9.0 <9.* | 10.*, 11.*, 12.*, 13.*, 14.*, 15.*, 16.*, 17.*, 18.*, 4.*, 5.*, 6.*, 7.*, 8.*, 9.* |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket