CVE-2017-15897

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.

Category

3.1
CVSS
Severity: Low
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.43%
Vendor Advisory nodejs.org
Affected: The Node.js Project Node.js
Published at:
Updated at:

References

Link Tags
https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/ vendor advisory issue tracking

Frequently Asked Questions

What is the severity of CVE-2017-15897?
CVE-2017-15897 has been scored as a low severity vulnerability.
How to fix CVE-2017-15897?
To fix CVE-2017-15897, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-15897 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-15897 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-15897?
CVE-2017-15897 affects The Node.js Project Node.js.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.