{"answers":{"affected":"2 open source packages ship an affected version, including sds. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25862 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25862 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25862 is a medium-severity vulnerability in sds, published on 13 May 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25862 and fix it if it is affected.\n\nWhat it is: CVE-2022-25862 is a medium-severity vulnerability in sds, published on 13 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-25862 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sds (npm): affected all versions up to 4.4.0; no fix listed\n- sds (npm): affected all versions up to 4.4.0; no fix listed\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-2022-25862/ (Markdown: https://insights.sbomify.com/CVE-2022-25862/index.md)","id":"CVE-2022-25862","markdown":"https://insights.sbomify.com/CVE-2022-25862/index.md","name":"CVE-2022-25862","record":{"aliases":["GHSA-ph28-wwfj-fv7f"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Prototype pollution in the sds library allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"sds","vendor":"sds_project"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"This affects the package sds from 0.0.0. The library could be tricked into adding or modifying properties of the Object.prototype by abusing the set function located in js/set.js. **Note:** This vulnerability derives from an incomplete fix to [CVE-2020-7618](https://security.snyk.io/vuln/SNYK-JS-SDS-564123)","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":false,"headline":"Prototype Pollution","id":"CVE-2022-25862","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Deserialization of Untrusted Data","id":"CVE-2022-25863"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.4.0"],"package":"sds","purl":null,"source":"GHSA-ph28-wwfj-fv7f"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.4.0"],"package":"sds","purl":"pkg:npm/sds","source":"GHSA-ph28-wwfj-fv7f"}],"prev":{"headline":"Remote code execution in simple-git","id":"CVE-2022-25860"},"products":["sds"],"published":"2022-05-13","related":[{"cvss_score":5.3,"headline":"Prototype Pollution in sds","id":"CVE-2020-7618","kev_date_added":null,"published":"2020-04-07"}],"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 sds library allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2022-25862/"}