Bug 1620215 (CVE-2018-7166)

Summary:	CVE-2018-7166 nodejs: Unintentional exposure of uninitialized memory
Product:	[Other] Security Response	Reporter:	Pedro Sampaio <psampaio>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	ahardin, athmanem, avibelli, bgeorges, bleanhar, ccoleman, dbeveniu, dedgar, eparis, hesilva, hhorak, jbalunas, jgoulding, jokerman, jorton, jpallich, jshepherd, krathod, lthon, mchappel, mrunge, mszynkie, nodejs-sig, pgallagh, piotr1212, rruss, sgallagh, tchollingsworth, thrcka, zsvetlik
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	nodejs 10.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 12:28:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1622137, 1622138, 1622149
Bug Blocks:	1620216

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 3 Scott Gayou 2018-08-24 13:32:50 UTC

Upstream Commit:

https://github.com/nodejs/node/commit/40a7beeddac9b9ec9ef5b49157daaf8470648b08

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.