{"answers":{"affected":"2 open source packages ship an affected version, including serialize-to-js. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5954 in the wild and no public exploit code.","fix":"Upgrade serialize-to-js to 1.0.0 or later.","what":"CVE-2017-5954 is a critical unsafe deserialization vulnerability in n/a, published on 10 Feb 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-5954 and fix it if it is affected.\n\nWhat it is: CVE-2017-5954 is a critical unsafe deserialization vulnerability in n/a, published on 10 Feb 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-5954 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- serialize-to-js (npm): affected all versions; fixed in 1.0.0\n- serialize-to-js (npm): affected all versions; fixed in 1.0.0\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-5954/ (Markdown: https://insights.sbomify.com/CVE-2017-5954/index.md)","id":"CVE-2017-5954","markdown":"https://insights.sbomify.com/CVE-2017-5954/index.md","name":"CVE-2017-5954","record":{"aliases":["GHSA-mm62-wxc8-cf7m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js serialization library","requires_auth":"none","summary":"Attackers can achieve arbitrary code execution by passing malicious JavaScript objects to the deserialize function in the serialize-to-js package.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"serialize-to-js","vendor":"serialize-to-js_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"An issue was discovered in the serialize-to-js package 0.5.0 for Node.js. Untrusted data passed into the deserialize() function can be exploited to achieve arbitrary code execution by passing a JavaScript Object with an Immediately Invoked Function Expression (IIFE).","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":"Code Execution Through IIFE in serialize-to-js","id":"CVE-2017-5954","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"deserialization","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-5956"},"packages":[{"ecosystem":"npm","fixed":["1.0.0"],"introduced":["0"],"last_affected":[],"package":"serialize-to-js","purl":null,"source":"GHSA-mm62-wxc8-cf7m"},{"ecosystem":"npm","fixed":["1.0.0"],"introduced":["0"],"last_affected":[],"package":"serialize-to-js","purl":"pkg:npm/serialize-to-js","source":"GHSA-mm62-wxc8-cf7m"}],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2017-5953"},"products":["n/a"],"published":"2017-02-10","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-15871","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":3.1,"headline":"regular expressions Cross-Site Scripting (XSS) vulnerability in serialize-to-js","id":"CVE-2019-16772","kev_date_added":null,"published":"2019-12-06"}],"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-08-05","vendors":["n/a"]},"summary":"Attackers can achieve arbitrary code execution by passing malicious JavaScript objects to the deserialize function in the serialize-to-js package.","url":"https://insights.sbomify.com/CVE-2017-5954/"}