Bug 1532534 (CVE-2017-15897)

Summary:	CVE-2017-15897 nodejs: Unitialized buffer due to incorrect encoding
Product:	[Other] Security Response	Reporter:	Andrej Nemec <anemec>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	alessandro.polidori, apevec, athmanem, bleanhar, ccoleman, chrisw, dedgar, dmcphers, hhorak, jgoulding, jjoyce, jkeck, jorton, jschluet, kbasil, lhh, lpeer, markmc, mburns, mrunge, nodejs-sig, rbryant, rhel8-maint, sclewis, sgallagh, slinaber, tchollingsworth, tdecacqu, thrcka, zsvetlik
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-08 03:36:30 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:	1532535
Bug Blocks:

Description Andrej Nemec 2018-01-09 09:33:55 UTC

Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, 'Buffer.alloc(0x100, "This is not correctly encoded", "hex");' The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases.

Versions 4.X and 6.X were not vulnerable.

The severity of this information disclosure vulnerability was low (due to the combination of coding errors that need to have been made in order to make it exploitable) and it has been assigned CVE-2017-15897.

External References:

https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/

Comment 1 Andrej Nemec 2018-01-09 09:34:47 UTC

Created nodejs tracking bugs for this issue:

Affects: fedora-27 [bug 1532535]