{"answers":{"affected":"2 open source packages ship an affected version, including ws. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10518 in the wild and no public exploit code.","fix":"Upgrade ws to 1.0.1 or later.","what":"CVE-2016-10518 is a high-severity denial of service vulnerability in HackerOne ws node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-10518 and fix it if it is affected.\n\nWhat it is: CVE-2016-10518 is a high-severity denial of service vulnerability in HackerOne ws node module, published on 31 May 2018. 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-2016-10518 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ws (npm): affected all versions; fixed in 1.0.1\n- ws (npm): affected all versions; fixed in 1.0.1\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-2016-10518/ (Markdown: https://insights.sbomify.com/CVE-2016-10518/index.md)","id":"CVE-2016-10518","markdown":"https://insights.sbomify.com/CVE-2016-10518/index.md","name":"CVE-2016-10518","record":{"aliases":["CLSA-2026-1784596272","DEBIAN-CVE-2016-10518","GHSA-2mhh-w6q8-5hxw","MINI-34m9-8mxh-7cxg","MINI-chmh-66jf-4pqx","UBUNTU-CVE-2016-10518"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js WebSocket library","requires_auth":"none","summary":"Attackers can cause denial of service in the ws Node.js library by sending ping frames that trigger excessive memory allocation.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"ws","vendor":"ws_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"},{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Remote Memory Disclosure in ws","id":"CVE-2016-10518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2016"},"n_packages":2,"n_references":3,"next":{"headline":"Remote Memory Disclosure in bittorrent-dht","id":"CVE-2016-10519"},"packages":[{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"ws","purl":null,"source":"GHSA-2mhh-w6q8-5hxw"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"ws","purl":"pkg:npm/ws","source":"GHSA-2mhh-w6q8-5hxw"}],"prev":{"headline":"Other in n/a","id":"CVE-2016-10517"},"products":["ws node module"],"published":"2018-05-31","related":[{"cvss_score":7.5,"headline":"ws: Memory exhaustion DoS from tiny fragments and data chunks","id":"CVE-2026-48779","kev_date_added":null,"published":"2026-06-16"},{"cvss_score":7.5,"headline":"DoS due to excessively large websocket message in ws","id":"CVE-2016-10542","kev_date_added":null,"published":"2018-05-31"},{"cvss_score":4.4,"headline":"ws: Uninitialized memory disclosure","id":"CVE-2026-45736","kev_date_added":null,"published":"2026-05-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["HackerOne"]},"summary":"Attackers can cause denial of service in the ws Node.js library by sending ping frames that trigger excessive memory allocation.","url":"https://insights.sbomify.com/CVE-2016-10518/"}