{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-3731 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-3731 is a high-severity memory corruption vulnerability in Nodejs Node.js, published on 4 May 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-3731 and fix it if it is affected.\n\nWhat it is: CVE-2017-3731 is a high-severity memory corruption vulnerability in Nodejs Node.js, published on 4 May 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-3731 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-3731/ (Markdown: https://insights.sbomify.com/CVE-2017-3731/index.md)","id":"CVE-2017-3731","markdown":"https://insights.sbomify.com/CVE-2017-3731/index.md","name":"CVE-2017-3731","record":{"aliases":["ALPINE-CVE-2017-3731","DEBIAN-CVE-2017-3731","GHSA-3cp9-4w64-73cg","UBUNTU-CVE-2017-3731"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenSSL library","requires_auth":"none","summary":"A truncated packet can cause an out-of-bounds read and crash in OpenSSL on 32-bit hosts using specific ciphers.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openssl","cpe":[{"product":"node.js","vendor":"nodejs"},{"product":"openssl","vendor":"openssl"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.","ecosystems":[],"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":"Truncated packet could crash via OOB read","id":"CVE-2017-3731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nodejs:node.js","products":["nodejs:node.js","openssl:openssl"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":20,"next":{"headline":"BN_mod_exp may produce incorrect results on x86_64","id":"CVE-2017-3732"},"packages":[],"prev":{"headline":"Bad (EC)DHE parameters cause a client crash","id":"CVE-2017-3730"},"products":["OpenSSL"],"published":"2017-05-04","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":"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":["OpenSSL"]},"summary":"A truncated packet can cause an out-of-bounds read and crash in OpenSSL on 32-bit hosts using specific ciphers.","url":"https://insights.sbomify.com/CVE-2017-3731/"}