First published: Sun Aug 12 2018(Updated: )
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.
Credit: cve-request@iojs.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/nodejs | <10.9.0 | 10.9.0 |
Langgenius Dify Node.js | >=10.0.0<10.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-7166 is considered a critical vulnerability due to the potential exposure of sensitive data through uninitialized memory.
To fix CVE-2018-7166, upgrade Node.js to version 10.9.0 or later.
CVE-2018-7166 affects all versions of Node.js prior to 10.9.0.
CVE-2018-7166 is categorized as an argument processing flaw in the Node.js Buffer module.
Yes, CVE-2018-7166 can lead to data exposure due to the returning of uninitialized memory.