CVE-2017-11499
published 2017-07-25CVE-2017-11499: 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…
PriorityP340high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
5.48%
91.9th percentile
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.
Affected
105 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | nodejs | < nodejs 4.8.4~dfsg-1 (bookworm) | nodejs 4.8.4~dfsg-1 (bookworm) |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5LOW
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-hc9r-2x24-2x3w: Node
ghsa_unreviewed·2022-05-17
CVE-2017-11499 [HIGH] CWE-20 GHSA-hc9r-2x24-2x3w: Node
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.
OSV
CVE-2017-11499: Node
osv·2017-07-25·CVSS 7.5
CVE-2017-11499 [HIGH] CVE-2017-11499: Node
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.
Red Hat
nodejs: Constant Hashtable Seeds vulnerability
vendor_redhat·2017-07-11·CVSS 7.5
CVE-2017-11499 [HIGH] nodejs: Constant Hashtable Seeds vulnerability
nodejs: Constant Hashtable Seeds vulnerability
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.
It was found that Node.js was using a non-randomized seed when populating hash tables. An attacker, able to supply a large number of inputs, could send specially crafted entries to the Node.js application, maximizing hash collisions to trigger an excessive amount of CPU usage, resulting in a denial of service.
Package: nodejs (Red Hat Enterprise Linux OpenSt
Debian
CVE-2017-11499: nodejs - Node.js v4.0 through v4.8.3, all versions of v5.x, v6.0 through v6.11.0, v7.0 th...
vendor_debian·2017·CVSS 7.5
CVE-2017-11499 [HIGH] CVE-2017-11499: nodejs - Node.js v4.0 through v4.8.3, all versions of v5.x, v6.0 through v6.11.0, v7.0 th...
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.
Scope: local
bookworm: resolved (fixed in 4.8.4~dfsg-1)
bullseye: resolved (fixed in 4.8.4~dfsg-1)
forky: resolved (fixed in 4.8.4~dfsg-1)
sid: resolved (fixed in 4.8.4~dfsg-1)
trixie: resolved (fixed in 4.8.4~dfsg-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability [fedora-all]
bugzilla·2017-07-26·CVSS 7.5
CVE-2017-11499 [HIGH] CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability [fedora-all]
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of
Bugzilla
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability
bugzilla·2017-07-26·CVSS 7.5
CVE-2017-11499 [HIGH] CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability
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.
External References:
https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/
Discussion:
Created nodejs tracking bugs for this issue:
Affects: epel-all [bug 1475330]
Affects: fedora-all [bug 1475328]
Affects: openshift-1 [bug 1475329]
---
Lowering severity to Medium to keep it aligned with similar remote DoS by hash table is
Bugzilla
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability [epel-all]
bugzilla·2017-07-26·CVSS 7.5
CVE-2017-11499 [HIGH] CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability [epel-all]
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fed
http://www.securityfocus.com/bid/99959https://access.redhat.com/errata/RHSA-2017:2908https://access.redhat.com/errata/RHSA-2017:3002https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/http://www.securityfocus.com/bid/99959https://access.redhat.com/errata/RHSA-2017:2908https://access.redhat.com/errata/RHSA-2017:3002https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/
2017-07-25
Published