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.

Risk Information

Base Score
3.1
MODERATE
Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score
Exploitation Probability
0.642

Associated Vulnerability

VulnerabilityOS Platform
Vulnerabilities CVE-2017-15896,CVE-2017-3737,CVE-2017-15897 are fixed in Node.js 10 (10.24.1)Windows
Vulnerabilities CVE-2017-15896,CVE-2017-3737,CVE-2017-15897 are fixed in Node.js 8 8.9.3Windows
Vulnerabilities CVE-2017-15896,CVE-2017-3737,CVE-2017-15897 are fixed in Node.js 8 (x64) 8.9.3Windows
Vulnerabilities CVE-2017-15896,CVE-2017-3737,CVE-2017-15897 are fixed in Node.js 9.2.1Windows
Vulnerabilities CVE-2017-15896,CVE-2017-3737,CVE-2017-15897 are fixed in Node.js 6.12.2Windows
Vulnerabilities CVE-2017-15896,CVE-2017-3737,CVE-2017-15897 are fixed in Node.js 4.8.7Windows

Patch Details

Click to see the patches provided by ManageEngine for this CVE
Patch IDPatch Description
PATCH-319042Node.js 10 (10.24.1)
PATCH-319042Node.js 10 (10.24.1)
PATCH-319042Node.js 10 (10.24.1)
PATCH-319042Node.js 10 (10.24.1)

References

https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234