vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2017-15897

LOW
3.1
CVSS Score
Published: December 11, 2017 at 09:00 PM UTC
Updated: June 17, 2026 at 01:08 AM UTC
1 product affected across 1 vendorNode.js

Using Node.js by The Node.js Project?

Get instant alerts when new vulnerabilities affect Node.js - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
LOW3.1
Exploit prediction
EPSS 2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Node.js· Node.js
95%
v ≥ 8.0v ≥ 9.08.0.0 ≤ v ≤ 8.8.18.9.0 ≤ v < 8.9.39.0.0 ≤ v < 9.2.1
Affected range stops below 8.9.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

x_refsource_CONFIRMIssue TrackingVendor Advisory
Source: [email protected]
https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/

CVSS

3.1LOW[email protected]
Attack Vector
NETWORK
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-665

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card