In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying `encoding` can be passed as a number, this is misinterpreted by `Buffer's` internal "fill" method as the `start` to a fill operation. This flaw may be abused where `Buffer.alloc()` arguments are derived from user input to return uncleared memory blocks that may contain sensitive information.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/ Vendor Advisory
- https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/ Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.5 · nodejsNVD modified 2026-10-08 22:16
Affected (CPE criteria) 1
cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*
References 4
- https://access.redhat.com/errata/RHSA-2018:2553 Third Party Advisory
- https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/ Vendor Advisory
- https://access.redhat.com/errata/RHSA-2018:2553 Third Party Advisory
- https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/ Vendor Advisory