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…
Noroxi assessment
Priority: Monitor (action score 32/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 5.4% (FIRST EPSS); higher than 92.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: nodejs (Debian:12) 4.8.4~dfsg-1; rh-nodejs4 (Red Hat:rhel_software_collections:2::el6) 0:2.4-4.el6; rh-nodejs4-node-gyp (Red Hat:rhel_software_collections:2::el6) 0:3.3.1-5.el6.
Low priority for now. Upgrade to nodejs (Debian:12) 4.8.4~dfsg-1; rh-nodejs4 (Red Hat:rhel_software_collections:2::el6) 0:2.4-4.el6; rh-nodejs4-node-gyp (Red Hat:rhel_software_collections:2::el6) 0:3.3.1-5.el6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2017
- Updated
- Jun 16, 2026
- EPSS
- 5.4% · 92th percentile
- CWE
- CWE-20
Report tools
Action score
32
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js4.0.0
- nodejs node.js4.1.0
- nodejs node.js4.1.1
- nodejs node.js4.1.2
- nodejs node.js4.2.0
- nodejs node.js4.2.1
- nodejs node.js4.2.2
- nodejs node.js4.2.3
+12 more rows
- nodejs node.js4.2.4
- nodejs node.js4.2.5
- nodejs node.js4.2.6
- nodejs node.js4.3.0
- nodejs node.js4.3.1
- nodejs node.js4.3.2
- nodejs node.js4.4.0
- nodejs node.js4.4.1
- nodejs node.js4.4.2
- nodejs node.js4.4.3
- nodejs node.js4.4.4
- nodejs node.js4.4.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | nodejs | before 4.8.4~dfsg-1 | 4.8.4~dfsg-1 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4 | before 0:2.4-4.el6 | 0:2.4-4.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-node-gyp | before 0:3.3.1-5.el6 | 0:3.3.1-5.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-nodejs | before 1:4.6.2-7.el6 | 1:4.6.2-7.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-nodejs-debuginfo | before 1:4.6.2-7.el6 | 1:4.6.2-7.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-nodejs-devel | before 1:4.6.2-7.el6 | 1:4.6.2-7.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-nodejs-docs | before 1:4.6.2-7.el6 | 1:4.6.2-7.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-runtime | before 0:2.4-4.el6 | 0:2.4-4.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs4-scldevel | before 0:2.4-4.el6 | 0:2.4-4.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs-debuginfo | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs-devel | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs-docs | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4 | before 0:2.4-3.el7 | 0:2.4-3.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4-nodejs | before 1:4.6.2-6.el7 | 1:4.6.2-6.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4-nodejs-debuginfo | before 1:4.6.2-6.el7 | 1:4.6.2-6.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4-nodejs-devel | before 1:4.6.2-6.el7 | 1:4.6.2-6.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4-nodejs-docs | before 1:4.6.2-6.el7 | 1:4.6.2-6.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4-runtime | before 0:2.4-3.el7 | 0:2.4-3.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs4-scldevel | before 0:2.4-3.el7 | 0:2.4-3.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs-debuginfo | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs-devel | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs-docs | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
+96
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an…53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory…50Plan
Published before and after this one in the same product
- ← EarlierCVE-2015-8855Jan 23, 2017 · The semver package before 4.3.2 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long version string, aka…32Monitor
- ← EarlierCVE-2015-8860Jan 23, 2017 · The tar package before 2.0.0 for Node.js allows remote attackers to write to arbitrary files via a symlink attack in an archive.31Monitor
- Later →CVE-2017-14849Sep 27, 2017 · Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the…46Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:nodejs | 4.8.4~dfsg-1 · Debian:12 | Package registry (OSV) |
| red hat:rh-nodejs4 | 0:2.4-4.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-node-gyp | 0:3.3.1-5.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-nodejs | 1:4.6.2-7.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-nodejs-debuginfo | 1:4.6.2-7.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-nodejs-devel | 1:4.6.2-7.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-nodejs-docs | 1:4.6.2-7.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-runtime | 0:2.4-4.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs4-scldevel | 0:2.4-4.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-debuginfo | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-devel | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-docs | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| suse:ardana-neutron | 9.0+git.1615223676.777f0b3-3.25.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:ardana-swift | 9.0+git.1618235096.90974ed-3.10.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:cassandra | 3.11.10-3.3.3 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:grafana | 6.7.4-3.23.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:kibana | 4.6.6-4.9.2 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:nodejs-common | 1.0-2.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:nodejs4 | 4.8.4-15.5.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:nodejs6 | 6.11.1-11.5.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:openstack-dashboard | 14.1.1~dev11-3.24.6 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-ironic | 11.1.5~dev17-3.25.5 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-neutron | 13.0.8~dev164-3.37.4 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
| suse:openstack-neutron-gbp | 12.0.1~dev29-3.25.3 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-04-07 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+3178 d
- TodayNov 16, 2026+3401 d
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.