Skip to content
Fencer Intel
low 3.1

CVE-2017-15897 json

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…

published 8y ago modified 4mo ago also EUVD-2017-7316

cvss
3.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • nodejs node.js 8.9.3, 9.2.1
  • firefox-atk SLES 11 SP4-LTSS 2.26.1-2.8.4
  • mozilla-nss SLES 11 SP4-LTSS 3.45-38.9.3
  • firefox-gtk3 SLES 11 SP4-LTSS 3.10.9-2.15.3
  • mozilla-nspr SLES 11 SP4-LTSS 4.21-29.6.1
  • firefox-cairo SLES 11 SP4-LTSS 1.15.10-2.13.4
  • firefox-glib2 SLES 11 SP4-LTSS 2.54.3-2.14.7
  • firefox-pango SLES 11 SP4-LTSS 1.40.14-2.7.4
  • firefox-libffi SLES 11 SP4-LTSS 3.2.1.git259-2.3.3

suse advisories SUSE-SU-2019:14246-1

  • nodejs Alpine 3.24, Alpine 3.23, Alpine 3.22 +15 more 8.9.3-r0
  • nodejs-current Alpine 3.24, Alpine 3.23, Alpine 3.22 +15 more 9.2.1-r0

alpine advisories ALPINE-CVE-2017-15897

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2017-15897 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-15897 updated cvss 3.7

nodejs: Unitialized buffer due to incorrect encoding

  • Red Hat Enterprise Linux 8 npm, nodejs, nodejs-libs, nodejs-nodemon, nodejs-full-i18n, nodejs-packaging, +1 more Red Hat Software Collections rh-nodejs8-npm, rh-nodejs8-nodejs
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) Operational Tools nodejs Red Hat OpenShift Enterprise 3 nodejs Red Hat OpenStack Platform 9 (Mitaka) Operational Tools nodejs Red Hat Software Collections nodejs010-nodejs, rh-nodejs4-nodejs, rh-nodejs6-nodejs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.32% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • The Node.js Project Node.js

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.