{"answers":{"affected":"2 open source packages ship an affected version, including json-ptr. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7766 in the wild and no public exploit code.","fix":"Upgrade json-ptr to 2.1.0 or later.","what":"CVE-2020-7766 is a high-severity vulnerability in json-ptr, 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-7766 and fix it if it is affected.\n\nWhat it is: CVE-2020-7766 is a high-severity vulnerability in json-ptr, 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-7766 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- json-ptr (npm): affected all versions; fixed in 2.1.0\n- json-ptr (npm): affected all versions; fixed in 2.1.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-2020-7766/ (Markdown: https://insights.sbomify.com/CVE-2020-7766/index.md)","id":"CVE-2020-7766","markdown":"https://insights.sbomify.com/CVE-2020-7766/index.md","name":"CVE-2020-7766","record":{"aliases":["GHSA-x5r6-x823-9848"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"npm json-ptr library","requires_auth":"none","summary":"Prototype pollution in json-ptr allows attackers to modify object prototypes when the force flag is enabled, 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":"json-ptr","vendor":"json-ptr_project"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"This affects all versions of package json-ptr. The issue occurs in the set operation (https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.","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-2020-7766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"Regular Expression Denial of Service (ReDoS)","id":"CVE-2020-7767"},"packages":[{"ecosystem":"npm","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"json-ptr","purl":null,"source":"GHSA-x5r6-x823-9848"},{"ecosystem":"npm","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"json-ptr","purl":"pkg:npm/json-ptr","source":"GHSA-x5r6-x823-9848"}],"prev":{"headline":"Prototype Pollution","id":"CVE-2020-7765"},"products":["json-ptr"],"published":"2020-11-10","related":[{"cvss_score":5.6,"headline":"Prototype Pollution","id":"CVE-2021-23509","kev_date_added":null,"published":"2021-11-03"}],"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 json-ptr allows attackers to modify object prototypes when the force flag is enabled, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2020-7766/"}