{"answers":{"affected":"2 open source packages ship an affected version, including mout. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7792 in the wild and no public exploit code.","fix":"Upgrade mout to 1.2.3 or later.","what":"CVE-2020-7792 is a high-severity vulnerability in mout, published on 11 Dec 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-7792 and fix it if it is affected.\n\nWhat it is: CVE-2020-7792 is a high-severity vulnerability in mout, published on 11 Dec 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-7792 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mout (npm): affected all versions; fixed in 1.2.3\n- mout (npm): affected all versions; fixed in 1.2.3\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-7792/ (Markdown: https://insights.sbomify.com/CVE-2020-7792/index.md)","id":"CVE-2020-7792","markdown":"https://insights.sbomify.com/CVE-2020-7792/index.md","name":"CVE-2020-7792","record":{"aliases":["CLSA-2026-1789117092","CLSA-2026-1792759966","GHSA-pc58-wgmc-hfjr"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Prototype pollution in the mout library allows attackers to manipulate 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":"mout","vendor":"moutjs"}],"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","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"This affects all versions of package mout. The deepFillIn function can be used to 'fill missing properties recursively', while the deepMixIn 'mixes objects into the target object, recursively mixing existing child objects as well'. In both cases, the key used to access the target object recursively is not checked, 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-7792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":5,"next":{"headline":"Regular Expression Denial of Service (ReDoS)","id":"CVE-2020-7793"},"packages":[{"ecosystem":"npm","fixed":["1.2.3"],"introduced":["0"],"last_affected":[],"package":"mout","purl":null,"source":"GHSA-pc58-wgmc-hfjr"},{"ecosystem":"npm","fixed":["1.2.3"],"introduced":["0"],"last_affected":[],"package":"mout","purl":"pkg:npm/mout","source":"GHSA-pc58-wgmc-hfjr"}],"prev":{"headline":"Denial of Service (DoS)","id":"CVE-2020-7791"},"products":["mout"],"published":"2020-12-11","related":[{"cvss_score":7.5,"headline":"Prototype Pollution","id":"CVE-2022-21213","kev_date_added":null,"published":"2022-06-17"}],"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 the mout library allows attackers to manipulate object prototypes, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2020-7792/"}