Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1532534 - (CVE-2017-15897) CVE-2017-15897 nodejs: Unitialized buffer due to incorrect encoding
CVE-2017-15897 nodejs: Unitialized buffer due to incorrect encoding
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20171207,reported=2...
: Security
Depends On: 1532535
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-09 04:33 EST by Andrej Nemec
Modified: 2018-07-30 06:28 EDT (History)
31 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2018-01-09 04:33:55 EST
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 04:34:47 EST
Created nodejs tracking bugs for this issue:

Affects: fedora-27 [bug 1532535]

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