CVE-2017-15897: Low severity Nodejs Node.js vulnerability

Published Dec 11, 2017
·
Updated

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 Software

40 affected componentsFixes available
Nodejs Node.js>=8.0.0<=8.8.1
Nodejs Node.js>=8.9.0<8.9.3
Nodejs Node.js>=9.0.0<9.2.1
Node.js Node.js>=8.0.0<8.9.3, >=9.0.0<9.2.1
8.9.39.2.1
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs<8.9.3-r0
8.9.3-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0
alpine/nodejs-current<9.2.1-r0
9.2.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.9.3Fixed in 9.2.1
  2. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 8.9.3-r0
  3. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 9.2.1-r0

Event History

Dec 11, 2017
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionWeakness
Data Sourced
via NVD·09:29 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·09:29 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2017-15897?

CVE-2017-15897 is considered a moderate severity vulnerability.

2

How do I fix CVE-2017-15897?

To fix CVE-2017-15897, upgrade Node.js to version 8.9.3 or later, or version 9.2.1 or later.

3

What versions of Node.js are affected by CVE-2017-15897?

CVE-2017-15897 affects Node.js versions 8.0.0 to 8.8.1, 8.9.0 to 8.9.2, and 9.0.0 to 9.2.0.

4

What is the impact of CVE-2017-15897?

The impact of CVE-2017-15897 is that uninitialized buffers can lead to information leaks in potentially sensitive data.

5

Is Node.js LTS affected by CVE-2017-15897?

Yes, certain versions of Node.js LTS are affected by CVE-2017-15897.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203