high
7.5
CWE
20
Advisory Published
Updated

CVE-2017-11499: Input Validation

First published: Tue Jul 25 2017(Updated: )

Node.js v4.0 through v4.8.3, all versions of v5.x, v6.0 through v6.11.0, v7.0 through v7.10.0, and v8.0 through v8.1.3 was susceptible to hash flooding remote DoS attacks as the HashTable seed was constant across a given released version of Node.js. This was a result of building with V8 snapshots enabled by default which caused the initially randomized seed to be overwritten on startup.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/nodejs<4.8.4
4.8.4
redhat/nodejs<6.11.1
6.11.1
redhat/nodejs<7.10.1
7.10.1
redhat/nodejs<8.1.4
8.1.4
Langgenius Dify Node.js=4.0.0
Langgenius Dify Node.js=4.1.0
Langgenius Dify Node.js=4.1.1
Langgenius Dify Node.js=4.1.2
Langgenius Dify Node.js=4.2.0
Langgenius Dify Node.js=4.2.1
Langgenius Dify Node.js=4.2.2
Langgenius Dify Node.js=4.2.3
Langgenius Dify Node.js=4.2.4
Langgenius Dify Node.js=4.2.5
Langgenius Dify Node.js=4.2.6
Langgenius Dify Node.js=4.3.0
Langgenius Dify Node.js=4.3.1
Langgenius Dify Node.js=4.3.2
Langgenius Dify Node.js=4.4.0
Langgenius Dify Node.js=4.4.1
Langgenius Dify Node.js=4.4.2
Langgenius Dify Node.js=4.4.3
Langgenius Dify Node.js=4.4.4
Langgenius Dify Node.js=4.4.5
Langgenius Dify Node.js=4.4.6
Langgenius Dify Node.js=4.4.7
Langgenius Dify Node.js=4.5.0
Langgenius Dify Node.js=4.6.0
Langgenius Dify Node.js=4.6.1
Langgenius Dify Node.js=4.6.2
Langgenius Dify Node.js=4.7.0
Langgenius Dify Node.js=4.7.1
Langgenius Dify Node.js=4.7.2
Langgenius Dify Node.js=4.7.3
Langgenius Dify Node.js=4.8.0
Langgenius Dify Node.js=4.8.1
Langgenius Dify Node.js=4.8.2
Langgenius Dify Node.js=4.8.3
Langgenius Dify Node.js=5.0.0
Langgenius Dify Node.js=5.1.0
Langgenius Dify Node.js=5.1.1
Langgenius Dify Node.js=5.2.0
Langgenius Dify Node.js=5.3.0
Langgenius Dify Node.js=5.4.0
Langgenius Dify Node.js=5.4.1
Langgenius Dify Node.js=5.5.0
Langgenius Dify Node.js=5.6.0
Langgenius Dify Node.js=5.7.0
Langgenius Dify Node.js=5.7.1
Langgenius Dify Node.js=5.8.0
Langgenius Dify Node.js=5.9.0
Langgenius Dify Node.js=5.9.1
Langgenius Dify Node.js=5.10.0
Langgenius Dify Node.js=5.10.1
Langgenius Dify Node.js=5.11.0
Langgenius Dify Node.js=5.11.1
Langgenius Dify Node.js=5.12.0
Langgenius Dify Node.js=6.0.0
Langgenius Dify Node.js=6.1.0
Langgenius Dify Node.js=6.2.0
Langgenius Dify Node.js=6.2.1
Langgenius Dify Node.js=6.2.2
Langgenius Dify Node.js=6.3.0
Langgenius Dify Node.js=6.3.1
Langgenius Dify Node.js=6.4.0
Langgenius Dify Node.js=6.5.0
Langgenius Dify Node.js=6.6.0
Langgenius Dify Node.js=6.7.0
Langgenius Dify Node.js=6.8.0
Langgenius Dify Node.js=6.8.1
Langgenius Dify Node.js=6.9.0
Langgenius Dify Node.js=6.9.1
Langgenius Dify Node.js=6.9.2
Langgenius Dify Node.js=6.9.3
Langgenius Dify Node.js=6.9.4
Langgenius Dify Node.js=6.9.5
Langgenius Dify Node.js=6.10.0
Langgenius Dify Node.js=6.10.1
Langgenius Dify Node.js=6.10.2
Langgenius Dify Node.js=6.10.3
Langgenius Dify Node.js=6.11.0
Langgenius Dify Node.js=6.11.1
Langgenius Dify Node.js=7.0.0
Langgenius Dify Node.js=7.1.0
Langgenius Dify Node.js=7.2.0
Langgenius Dify Node.js=7.2.1
Langgenius Dify Node.js=7.3.0
Langgenius Dify Node.js=7.4.0
Langgenius Dify Node.js=7.5.0
Langgenius Dify Node.js=7.6.0
Langgenius Dify Node.js=7.7.0
Langgenius Dify Node.js=7.7.1
Langgenius Dify Node.js=7.7.2
Langgenius Dify Node.js=7.7.3
Langgenius Dify Node.js=7.7.4
Langgenius Dify Node.js=7.8.0
Langgenius Dify Node.js=7.9.0
Langgenius Dify Node.js=7.10.0
Langgenius Dify Node.js=7.10.1
Langgenius Dify Node.js=8.0.0
Langgenius Dify Node.js=8.1.0
Langgenius Dify Node.js=8.1.1
Langgenius Dify Node.js=8.1.2
Langgenius Dify Node.js=8.1.3

Remedy

https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2017-11499?

    CVE-2017-11499 has been classified as a high severity vulnerability due to its potential to cause remote denial of service (DoS) attacks.

  • How do I fix CVE-2017-11499?

    To fix CVE-2017-11499, update to Node.js versions 4.8.4, 6.11.1, 7.10.1, or 8.1.4 or later.

  • Which versions of Node.js are affected by CVE-2017-11499?

    CVE-2017-11499 affects Node.js versions from 4.0 to 4.8.3, all versions of 5.x, versions 6.0 to 6.11.0, versions 7.0 to 7.10.0, and versions 8.0 to 8.1.3.

  • What type of attack does CVE-2017-11499 enable?

    CVE-2017-11499 enables hash flooding remote denial of service (DoS) attacks.

  • Is CVE-2017-11499 specific to any operating system?

    CVE-2017-11499 is primarily associated with the Node.js application and its associated environments rather than specific operating systems.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203