{"answers":{"affected":"2 open source packages ship an affected version, including @strikeentco/set. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-23497 in the wild and no public exploit code.","fix":"Upgrade @strikeentco/set to 1.0.2 or later.","what":"CVE-2021-23497 is a high-severity vulnerability in @strikeentco/set, 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-23497 and fix it if it is affected.\n\nWhat it is: CVE-2021-23497 is a high-severity vulnerability in @strikeentco/set, 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-23497 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @strikeentco/set (npm): affected all versions; fixed in 1.0.2\n- @strikeentco/set (npm): affected all versions; fixed in 1.0.2\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-23497/ (Markdown: https://insights.sbomify.com/CVE-2021-23497/index.md)","id":"CVE-2021-23497","markdown":"https://insights.sbomify.com/CVE-2021-23497/index.md","name":"CVE-2021-23497","record":{"aliases":["GHSA-39qv-prmh-x37f","SNYK-JS-STRIKEENTCOSET-2385945"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Prototype pollution in the @strikeentco/set library allows attackers to cause denial of service and potentially execute remote code.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"set","vendor":"set_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"This affects the package @strikeentco/set before 1.0.2. It allows an attacker to cause a denial of service and may lead to remote code execution. **Note:** This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-STRIKEENTCOSET-1038821","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-23497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"Prototype Pollution","id":"CVE-2021-23507"},"packages":[{"ecosystem":"npm","fixed":["1.0.2"],"introduced":["0"],"last_affected":[],"package":"@strikeentco/set","purl":null,"source":"GHSA-39qv-prmh-x37f"},{"ecosystem":"npm","fixed":["1.0.2"],"introduced":["0"],"last_affected":[],"package":"@strikeentco/set","purl":"pkg:npm/%40strikeentco/set","source":"GHSA-39qv-prmh-x37f"}],"prev":{"headline":"Open Redirect","id":"CVE-2021-23495"},"products":["@strikeentco/set"],"published":"2022-02-04","related":[{"cvss_score":7.5,"headline":"Prototype pollution in @strikeentco/set","id":"CVE-2020-28267","kev_date_added":null,"published":"2020-11-10"}],"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":"Prototype pollution in the @strikeentco/set library allows attackers to cause denial of service and potentially execute remote code.","url":"https://insights.sbomify.com/CVE-2021-23497/"}