Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Node.Js | >= 10.0.0, < 10.9.0 |
Related Weaknesses (CWE)
References
- https://access.redhat.com/errata/RHSA-2018:2553Third Party Advisory
- https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/Vendor Advisory
- https://access.redhat.com/errata/RHSA-2018:2553Third Party Advisory
- https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/Vendor Advisory
FAQ
What is CVE-2018-7166?
CVE-2018-7166 is a vulnerability with a CVSS score of 7.5 (HIGH). 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...
How severe is CVE-2018-7166?
CVE-2018-7166 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2018-7166?
Check the references section above for vendor advisories and patch information. Affected products include: Nodejs Node.Js.