{"answers":{"affected":"2 open source packages ship an affected version, including putil-merge. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-23470 in the wild and no public exploit code.","fix":"Upgrade putil-merge to 3.8.0 or later.","what":"CVE-2021-23470 is a high-severity vulnerability in putil-merge, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-23470 and fix it if it is affected.\n\nWhat it is: CVE-2021-23470 is a high-severity vulnerability in putil-merge, published on 4 Feb 2022. 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-2021-23470 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- putil-merge (npm): affected all versions; fixed in 3.8.0\n- putil-merge (npm): affected all versions; fixed in 3.8.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-2021-23470/ (Markdown: https://insights.sbomify.com/CVE-2021-23470/index.md)","id":"CVE-2021-23470","markdown":"https://insights.sbomify.com/CVE-2021-23470/index.md","name":"CVE-2021-23470","record":{"aliases":["GHSA-4g77-cvgw-grvw","SNYK-JS-PUTILMERGE-2391487"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript merge library","requires_auth":"none","summary":"Attackers can exploit prototype pollution in putil-merge to potentially execute code or escalate privileges via malicious constructor properties.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"putil-merge","vendor":"putil-merge_project"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"This affects the package putil-merge before 3.8.0. The merge() function does not check the values passed into the argument. An attacker can supply a malicious value by adjusting the value to include the constructor property. Note: This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-PUTILMERGE-1317077","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":"Prototype Pollution","id":"CVE-2021-23470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site Scripting (XSS)","id":"CVE-2021-23472"},"packages":[{"ecosystem":"npm","fixed":["3.8.0"],"introduced":["0"],"last_affected":[],"package":"putil-merge","purl":null,"source":"GHSA-4g77-cvgw-grvw"},{"ecosystem":"npm","fixed":["3.8.0"],"introduced":["0"],"last_affected":[],"package":"putil-merge","purl":"pkg:npm/putil-merge","source":"GHSA-4g77-cvgw-grvw"}],"prev":{"headline":"XML External Entity (XXE) Injection","id":"CVE-2021-23463"},"products":["putil-merge"],"published":"2022-02-04","related":[{"cvss_score":9.8,"headline":"Prototype Pollution in putil-merge","id":"CVE-2021-25953","kev_date_added":null,"published":"2021-07-14"}],"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":["n/a"]},"summary":"Attackers can exploit prototype pollution in putil-merge to potentially execute code or escalate privileges via malicious constructor properties.","url":"https://insights.sbomify.com/CVE-2021-23470/"}