This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1475327 - (CVE-2017-11499) CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability
CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 1475329 1475613 1476314 1476315 1476316 1475328 1475330 1476317
Blocks: 1475332
  Show dependency treegraph
Reported: 2017-07-26 08:51 EDT by Adam Mariš
Modified: 2017-10-18 03:51 EDT (History)
35 users (show)

See Also:
Fixed In Version: nodejs 4.8.4, nodejs 6.11.1, nodejs 7.10.1, nodejs 8.1.4
Doc Type: If docs needed, set a value
Doc Text:
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.
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-07-26 08:51:34 EDT
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:
Comment 1 Adam Mariš 2017-07-26 08:52:26 EDT
Created nodejs tracking bugs for this issue:

Affects: epel-all [bug 1475330]
Affects: fedora-all [bug 1475328]
Affects: openshift-1 [bug 1475329]
Comment 3 Cedric Buissart 2017-07-28 05:45:48 EDT
Lowering severity to Medium to keep it aligned with similar remote DoS by hash table issues.
Comment 9 Cedric Buissart 2017-08-01 09:24:36 EDT
The upstream fix pointed in the upstream release note (commit 51d69d2bec) was a temporary fix only, aimed at disabling snapshot by default, and had a negative performance impact during creation of contexts (e.g.: vm.runInNewContext() calls).

A later patch re-enables snapshot by default, and adds re-hashing after de-serialization as mitigation :
Comment 10 errata-xmlrpc 2017-10-18 03:51:45 EDT
This issue has been addressed in the following products:

  Red Hat Software Collections for Red Hat Enterprise Linux 6
  Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7
  Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS

Via RHSA-2017:2908

Note You need to log in before you can comment on or make changes to this bug.