CVE-2017-15897
mediumpriority · track · 13EPSS 0.023 · 83 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.9–4.3
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (5)
Products and version ranges known to be affected.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (5)
External citations — patches, advisories, analysis.
- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/cnnvd
- https://www.auscert.org.au/bulletins/ESB-2019.4645/cnnvd
- https://www.suse.com/support/update/announcement/2019/suse-su-201914246-1.htmlcnnvd
- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/enisa_euvd
- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/Issue TrackingVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan