{"answers":{"affected":"2 open source packages ship an affected version, including deep-get-set. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21231 is a high-severity vulnerability in deep-get-set, published on 24 Jun 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-2022-21231 and fix it if it is affected.\n\nWhat it is: CVE-2022-21231 is a high-severity vulnerability in deep-get-set, published on 24 Jun 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-2022-21231 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- deep-get-set (npm): affected all versions up to 1.1.1; no fix listed\n- deep-get-set (npm): affected all versions up to 1.1.1; 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-21231/ (Markdown: https://insights.sbomify.com/CVE-2022-21231/index.md)","id":"CVE-2022-21231","markdown":"https://insights.sbomify.com/CVE-2022-21231/index.md","name":"CVE-2022-21231","record":{"aliases":["GHSA-mjjj-6p43-vhhv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Prototype pollution in deep-get-set allows attackers to modify object prototypes, 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":"deep-get-set","vendor":"deep-get-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":"All versions of package deep-get-set are vulnerable to Prototype Pollution via the 'deep' function. **Note:** This vulnerability derives from an incomplete fix of [CVE-2020-7715](https://security.snyk.io/vuln/SNYK-JS-DEEPGETSET-598666)","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-21231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in Intel(R) Processors","id":"CVE-2022-21233"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.1"],"package":"deep-get-set","purl":null,"source":"GHSA-mjjj-6p43-vhhv"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.1"],"package":"deep-get-set","purl":"pkg:npm/deep-get-set","source":"GHSA-mjjj-6p43-vhhv"}],"prev":{"headline":"Information Exposure","id":"CVE-2022-21230"},"products":["deep-get-set"],"published":"2022-06-24","related":[{"cvss_score":9.8,"headline":"Prototype Pollution","id":"CVE-2020-7715","kev_date_added":null,"published":"2020-09-01"}],"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-17","vendors":["n/a"]},"summary":"Prototype pollution in deep-get-set allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2022-21231/"}