CVE-2018-7166

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*

History

21 Nov 2024, 04:11

Type Values Removed Values Added
References () https://access.redhat.com/errata/RHSA-2018:2553 - Third Party Advisory () https://access.redhat.com/errata/RHSA-2018:2553 - Third Party Advisory
References () https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/ - Vendor Advisory () https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/ - Vendor Advisory

Information

Published : 2018-08-21 12:29

Updated : 2024-11-21 04:11


NVD link : CVE-2018-7166

Mitre link : CVE-2018-7166

CVE.ORG link : CVE-2018-7166


JSON object : View

Products Affected

nodejs

  • node.js
CWE
CWE-226

Sensitive Information in Resource Not Removed Before Reuse

CWE-908

Use of Uninitialized Resource