{"answers":{"affected":"2 open source packages ship an affected version, including socket.io. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16031 in the wild and no public exploit code.","fix":"Upgrade socket.io to 0.9.7 or later.","what":"CVE-2017-16031 is a high-severity vulnerability in HackerOne socket.io node module, published on 4 Jun 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-2017-16031 and fix it if it is affected.\n\nWhat it is: CVE-2017-16031 is a high-severity vulnerability in HackerOne socket.io node module, published on 4 Jun 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-2017-16031 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- socket.io (npm): affected all versions; fixed in 0.9.7\n- socket.io (npm): affected all versions; fixed in 0.9.7\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-16031/ (Markdown: https://insights.sbomify.com/CVE-2017-16031/index.md)","id":"CVE-2017-16031","markdown":"https://insights.sbomify.com/CVE-2017-16031/index.md","name":"CVE-2017-16031","record":{"aliases":["GHSA-qv2v-m59f-v5fw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Socket.io Node module","requires_auth":"none","summary":"Predictable socket IDs allow attackers to hijack connections and access sensitive data on Socket.io servers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"socket.io","vendor":"socket"}],"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-330","name":"Use of Insufficiently Random Values"}],"description":"Socket.io is a realtime application framework that provides communication via websockets. Because socket.io 0.9.6 and earlier depends on `Math.random()` to create socket IDs, the IDs are predictable. An attacker is able to guess the socket ID and gain access to socket.io servers, potentially obtaining sensitive information.","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":"Insecure randomness in socket.io","id":"CVE-2017-16031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"hubl-server downloads resources over HTTP","id":"CVE-2017-16035"},"packages":[{"ecosystem":"npm","fixed":["0.9.7"],"introduced":["0"],"last_affected":[],"package":"socket.io","purl":null,"source":"GHSA-qv2v-m59f-v5fw"},{"ecosystem":"npm","fixed":["0.9.7"],"introduced":["0"],"last_affected":[],"package":"socket.io","purl":"pkg:npm/socket.io","source":"GHSA-qv2v-m59f-v5fw"}],"prev":{"headline":"ReDoS via long UserAgent header in useragent","id":"CVE-2017-16030"},"products":["socket.io node module"],"published":"2018-06-04","related":[{"cvss_score":5.3,"headline":"Insecure Defaults","id":"CVE-2020-28481","kev_date_added":null,"published":"2021-01-19"}],"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-16","vendors":["HackerOne"]},"summary":"Predictable socket IDs allow attackers to hijack connections and access sensitive data on Socket.io servers.","url":"https://insights.sbomify.com/CVE-2017-16031/"}