{"answers":{"affected":"4 open source packages ship an affected version, including assign-deep. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10745 in the wild and no public exploit code.","fix":"Upgrade assign-deep to a fixed version for your release line: 0.4.8 or 1.0.1.","what":"CVE-2019-10745 is a high-severity vulnerability in assign-deep, published on 20 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10745 and fix it if it is affected.\n\nWhat it is: CVE-2019-10745 is a high-severity vulnerability in assign-deep, published on 20 Aug 2019. 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-2019-10745 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- assign-deep (npm): affected all versions; fixed in 0.4.8\n- assign-deep (npm): affected all versions; fixed in 0.4.8\n- assign-deep (npm): affected from 1.0.0; fixed in 1.0.1\n- assign-deep (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-2019-10745/ (Markdown: https://insights.sbomify.com/CVE-2019-10745/index.md)","id":"CVE-2019-10745","markdown":"https://insights.sbomify.com/CVE-2019-10745/index.md","name":"CVE-2019-10745","record":{"aliases":["GHSA-66rh-8fw6-59q6"],"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 assign-deep 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":"assign-deep","vendor":"assign-deep_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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"assign-deep is vulnerable to Prototype Pollution in versions before 0.4.8 and version 1.0.0. The function assign-deep could be tricked into adding or modifying properties of Object.prototype using either a constructor or a _proto_ payload.","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":"assign-deep Vulnerable to Prototype Pollution","id":"CVE-2019-10745","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2019"},"n_packages":4,"n_references":1,"next":{"headline":"Prototype Pollution in mixin-deep","id":"CVE-2019-10746"},"packages":[{"ecosystem":"npm","fixed":["0.4.8"],"introduced":["0"],"last_affected":[],"package":"assign-deep","purl":null,"source":"GHSA-66rh-8fw6-59q6"},{"ecosystem":"npm","fixed":["0.4.8"],"introduced":["0"],"last_affected":[],"package":"assign-deep","purl":"pkg:npm/assign-deep","source":"GHSA-66rh-8fw6-59q6"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["1.0.0"],"last_affected":[],"package":"assign-deep","purl":null,"source":"GHSA-66rh-8fw6-59q6"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["1.0.0"],"last_affected":[],"package":"assign-deep","purl":"pkg:npm/assign-deep","source":"GHSA-66rh-8fw6-59q6"}],"prev":{"headline":"Prototype Pollution in lodash","id":"CVE-2019-10744"},"products":["assign-deep"],"published":"2019-08-20","related":[{"cvss_score":8.8,"headline":"Prototype Pollution in assign-deep","id":"CVE-2018-3720","kev_date_added":null,"published":"2018-06-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-08-04","vendors":["n/a"]},"summary":"Prototype pollution in assign-deep allows attackers to modify Object.prototype, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2019-10745/"}