{"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-2020-28267 in the wild and no public exploit code.","fix":"Upgrade @strikeentco/set to 1.0.1 or later.","what":"CVE-2020-28267 is a high-severity vulnerability in @strikeentco/set, published on 10 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28267 and fix it if it is affected.\n\nWhat it is: CVE-2020-28267 is a high-severity vulnerability in @strikeentco/set, published on 10 Nov 2020. 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-2020-28267 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @strikeentco/set (npm): affected from 1.0.0; fixed in 1.0.1\n- @strikeentco/set (npm): affected from 1.0.0; fixed in 1.0.1\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-2020-28267/ (Markdown: https://insights.sbomify.com/CVE-2020-28267/index.md)","id":"CVE-2020-28267","markdown":"https://insights.sbomify.com/CVE-2020-28267/index.md","name":"CVE-2020-28267","record":{"aliases":["GHSA-wwg2-2crq-6grr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm utility library","requires_auth":"none","summary":"Prototype pollution in the @strikeentco/set npm 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":"Mend","cpe":[{"product":"set","vendor":"set_project"}],"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":[],"description":"Prototype pollution vulnerability in '@strikeentco/set' version 1.0.0 allows attacker to cause a denial of service and may lead to remote code execution.","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 in @strikeentco/set","id":"CVE-2020-28267","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Prototype pollution in controlled-merge","id":"CVE-2020-28268"},"packages":[{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["1.0.0"],"last_affected":[],"package":"@strikeentco/set","purl":null,"source":"GHSA-wwg2-2crq-6grr"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["1.0.0"],"last_affected":[],"package":"@strikeentco/set","purl":"pkg:npm/%40strikeentco/set","source":"GHSA-wwg2-2crq-6grr"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-28251"},"products":["@strikeentco/set"],"published":"2020-11-10","related":[{"cvss_score":7.5,"headline":"Prototype Pollution","id":"CVE-2021-23497","kev_date_added":null,"published":"2022-02-04"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Prototype pollution in the @strikeentco/set npm library allows attackers to cause denial of service and potentially execute remote code.","url":"https://insights.sbomify.com/CVE-2020-28267/"}