Bug 1620215 (CVE-2018-7166) - CVE-2018-7166 nodejs: Unintentional exposure of uninitialized memory
Summary: CVE-2018-7166 nodejs: Unintentional exposure of uninitialized memory
Keywords:
Status: NEW
Alias: CVE-2018-7166
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1622137 1622138 1622149
Blocks: 1620216
TreeView+ depends on / blocked
 
Reported: 2018-08-22 17:31 UTC by Pedro Sampaio
Modified: 2020-05-13 10:10 UTC (History)
30 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2553 None None None 2018-08-22 21:14:44 UTC

Description Pedro Sampaio 2018-08-22 17:31:30 UTC
Node.js TSC member Сковорода Никита Андреевич (Nikita Skovoroda / @ChALkeR) discovered an argument processing flaw that causes 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.

Impact:

All versions of Node.js 6.x (LTS "Boron") are NOT vulnerable
All versions of Node.js 8.x (LTS "Carbon") are NOT vulnerable
All previous versions of Node.js 10.x (Current) are vulnerable

References:

https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/

Comment 1 errata-xmlrpc 2018-08-22 21:14:31 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Application Runtimes Node.js 10

Via RHSA-2018:2553 https://access.redhat.com/errata/RHSA-2018:2553

Comment 2 Scott Gayou 2018-08-23 21:22:13 UTC
Release was updated to state: "Only Node.js 10 is impacted by this flaw. Our previous announcement wrongly stated that all release lines were vulnerable."

Comment 4 Scott Gayou 2018-08-24 14:22:04 UTC
Created nodejs tracking bugs for this issue:

Affects: fedora-all [bug 1622137]

Comment 8 Joshua Padman 2019-07-31 04:37:18 UTC
The current version rhoar-nodejs10-10.16.0-1.el7 was rebased to upstream and contains fixes.


Note You need to log in before you can comment on or make changes to this bug.