{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11499 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-11499 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 25 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-11499 and fix it if it is affected.\n\nWhat it is: CVE-2017-11499 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 25 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-11499 in the wild and no public exploit code.\n\nAffected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-11499/ (Markdown: https://insights.sbomify.com/CVE-2017-11499/index.md)","id":"CVE-2017-11499","markdown":"https://insights.sbomify.com/CVE-2017-11499/index.md","name":"CVE-2017-11499","record":{"aliases":["DEBIAN-CVE-2017-11499","GHSA-hc9r-2x24-2x3w","RHSA-2017:3002","UBUNTU-CVE-2017-11499"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js runtime","requires_auth":"none","summary":"Remote attackers can cause denial of service in Node.js via hash flooding due to a constant hash table seed caused by V8 snapshots.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"node.js","vendor":"nodejs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":["Red Hat:rhel_software_collections:2::el6","Red Hat:rhel_software_collections:2::el7"],"exploits":{"exploitdb":0,"first_seen":"2026-04-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-07T07:10:58Z","kind":"github_poc","ref":"https://github.com/open-flaw/CVE-2017-11499","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Denial of service in n/a","id":"CVE-2017-11499","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nodejs:node.js","products":["nodejs:node.js"],"type":"denial_of_service","year":"2017"},"n_packages":15,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2017-11500"},"packages":[{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["0:2.4-4.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4","purl":"pkg:rpm/redhat/rh-nodejs4","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["0:3.3.1-5.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-node-gyp","purl":"pkg:rpm/redhat/rh-nodejs4-node-gyp","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["1:4.6.2-7.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["1:4.6.2-7.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs-debuginfo","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs-debuginfo","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["1:4.6.2-7.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs-devel","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs-devel","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["1:4.6.2-7.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs-docs","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs-docs","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["0:2.4-4.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-runtime","purl":"pkg:rpm/redhat/rh-nodejs4-runtime","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el6","fixed":["0:2.4-4.el6"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-scldevel","purl":"pkg:rpm/redhat/rh-nodejs4-scldevel","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["0:2.4-3.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4","purl":"pkg:rpm/redhat/rh-nodejs4","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["1:4.6.2-6.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["1:4.6.2-6.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs-debuginfo","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs-debuginfo","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["1:4.6.2-6.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs-devel","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs-devel","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["1:4.6.2-6.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-nodejs-docs","purl":"pkg:rpm/redhat/rh-nodejs4-nodejs-docs","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["0:2.4-3.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-runtime","purl":"pkg:rpm/redhat/rh-nodejs4-runtime","source":"RHSA-2017:3002"},{"ecosystem":"Red Hat:rhel_software_collections:2::el7","fixed":["0:2.4-3.el7"],"introduced":["0"],"last_affected":[],"package":"rh-nodejs4-scldevel","purl":"pkg:rpm/redhat/rh-nodejs4-scldevel","source":"RHSA-2017:3002"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-11498"},"products":["n/a"],"published":"2017-07-25","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Node","id":"CVE-2023-32002","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-6303","kev_date_added":null,"published":"2016-09-16"},{"cvss_score":9.1,"headline":"Security feature bypass in Node.js","id":"CVE-2017-15896","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.8,"headline":"Server-side request forgery in Node.js","id":"CVE-2018-7160","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":8.1,"headline":"Misconfiguration in Node.js","id":"CVE-2018-12120","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21891","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21896","kev_date_added":null,"published":"2024-02-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service in Node.js via hash flooding due to a constant hash table seed caused by V8 snapshots.","url":"https://insights.sbomify.com/CVE-2017-11499/"}