https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:28:02 +0000 https://cve.radiocsirt.org/vuln/cnvd-2017-28420 cnvd-2017-28420 https://cve.radiocsirt.org/vuln/cnvd-2017-28420 https://cve.radiocsirt.org/vuln/euvd-2026-76778 EUVD-2026-76778 https://cve.radiocsirt.org/vuln/euvd-2026-76778 https://cve.radiocsirt.org/vuln/fkie_cve-2017-11499 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-11499 https://cve.radiocsirt.org/vuln/ghsa-hc9r-2x24-2x3w <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-hc9r-2x24-2x3w https://cve.radiocsirt.org/vuln/gsd-2017-11499 gsd-2017-11499 https://cve.radiocsirt.org/vuln/gsd-2017-11499 https://cve.radiocsirt.org/vuln/rhsa-2017:2908 <p>nodejs: Constant Hashtable Seeds vulnerability c-ares: NAPTR parser out of bounds access</p> <p>nodejs: Constant Hashtable Seeds vulnerability c-ares: NAPTR parser out of bounds access</p> https://cve.radiocsirt.org/vuln/rhsa-2017:2908 https://cve.radiocsirt.org/vuln/suse-su-2017:2168-1 <p>Security update for nodejs4, nodejs6</p> <p>Security update for nodejs4, nodejs6</p> https://cve.radiocsirt.org/vuln/suse-su-2017:2168-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-11499 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: nodejs</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: nodejs</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-11499