CVE-2017-11499
Last modified
CVE-2017-11499 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 5.48% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Node.Js | 4.0.0 |
| Nodejs | Node.Js | 4.1.0 |
| Nodejs | Node.Js | 4.1.1 |
| Nodejs | Node.Js | 4.1.2 |
| Nodejs | Node.Js | 4.2.0 |
| Nodejs | Node.Js | 4.2.1 |
| Nodejs | Node.Js | 4.2.2 |
| Nodejs | Node.Js | 4.2.3 |
| Nodejs | Node.Js | 4.2.4 |
| Nodejs | Node.Js | 4.2.5 |
| Nodejs | Node.Js | 4.2.6 |
| Nodejs | Node.Js | 4.3.0 |
| Nodejs | Node.Js | 4.3.1 |
| Nodejs | Node.Js | 4.3.2 |
| Nodejs | Node.Js | 4.4.0 |
| Nodejs | Node.Js | 4.4.1 |
| Nodejs | Node.Js | 4.4.2 |
| Nodejs | Node.Js | 4.4.3 |
| Nodejs | Node.Js | 4.4.4 |
| Nodejs | Node.Js | 4.4.5 |
| Nodejs | Node.Js | 4.4.6 |
| Nodejs | Node.Js | 4.4.7 |
| Nodejs | Node.Js | 4.5.0 |
| Nodejs | Node.Js | 4.6.0 |
| Nodejs | Node.Js | 4.6.1 |
| Nodejs | Node.Js | 4.6.2 |
| Nodejs | Node.Js | 4.7.0 |
| Nodejs | Node.Js | 4.7.1 |
| Nodejs | Node.Js | 4.7.2 |
| Nodejs | Node.Js | 4.7.3 |
| Nodejs | Node.Js | 4.8.0 |
| Nodejs | Node.Js | 4.8.1 |
| Nodejs | Node.Js | 4.8.2 |
| Nodejs | Node.Js | 4.8.3 |
| Nodejs | Node.Js | 5.0.0 |
| Nodejs | Node.Js | 5.1.0 |
| Nodejs | Node.Js | 5.1.1 |
| Nodejs | Node.Js | 5.2.0 |
| Nodejs | Node.Js | 5.3.0 |
| Nodejs | Node.Js | 5.4.0 |
| Nodejs | Node.Js | 5.4.1 |
| Nodejs | Node.Js | 5.5.0 |
| Nodejs | Node.Js | 5.6.0 |
| Nodejs | Node.Js | 5.7.0 |
| Nodejs | Node.Js | 5.7.1 |
| Nodejs | Node.Js | 5.8.0 |
| Nodejs | Node.Js | 5.9.0 |
| Nodejs | Node.Js | 5.9.1 |
| Nodejs | Node.Js | 5.10.0 |
| Nodejs | Node.Js | 5.10.1 |
Showing 50 of 100 affected configurations. See NVD for the full list.
References
- http://www.securityfocus.com/bid/99959Third Party Advisory, VDB Entry
- https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/Patch, Vendor Advisory
- http://www.securityfocus.com/bid/99959Third Party Advisory, VDB Entry
- https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-11499?
How severe is CVE-2017-11499?
How do I fix CVE-2017-11499?
Are you affected by CVE-2017-11499?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
