Bug 1475327 (CVE-2017-11499)
Summary: | CVE-2017-11499 nodejs: Constant Hashtable Seeds vulnerability | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Adam Mariš <amaris> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | abhgupta, ahardin, aortega, apevec, ayoung, bleanhar, cbuissar, ccoleman, chrisw, cvsbot-xmlrpc, dbaker, dedgar, dmcphers, hhorak, jgoulding, jjoyce, jkeck, jokerman, jorton, jschluet, kbasil, kseifried, lhh, lpeer, markmc, mchappel, mrunge, nodejs-sig, piotr1212, rbryant, sascha.vujevic, sclewis, sgallagh, tchollingsworth, tdecacqu, thrcka, tiwillia, zsvetlik |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
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: | Environment: | ||
Last Closed: | 2017-10-23 15:22:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1475328, 1475329, 1475330, 1475613, 1476314, 1476315, 1476316, 1476317 | ||
Bug Blocks: | 1475332 |
Description
Adam Mariš
2017-07-26 12:51:34 UTC
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 issues. 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 : https://github.com/nodejs/node/commit/8dce05fa 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 https://access.redhat.com/errata/RHSA-2017:2908 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:3002 https://access.redhat.com/errata/RHSA-2017:3002 Openshift Enterprise uses latest RHSCL nodejs-4-rhel7 image which contains a fix for this issue. Marking Openshift Enterprise as not affected. https://github.com/openshift/library/blob/4e6ba65846f803063b1d977eaa57c89af440812f/official/nodejs/imagestreams/nodejs-rhel7.json#L64 Marking Openshift Online as not affected for the same reasons as comment 12. |