{"answers":{"affected":"2 open source packages ship an affected version, including assign-deep. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3720 in the wild and no public exploit code.","fix":"Upgrade assign-deep to 0.4.7 or later.","what":"CVE-2018-3720 is a high-severity vulnerability in HackerOne assign-deep node module, published on 7 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3720 and fix it if it is affected.\n\nWhat it is: CVE-2018-3720 is a high-severity vulnerability in HackerOne assign-deep node module, published on 7 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-3720 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.7\n- assign-deep (npm): affected all versions; fixed in 0.4.7\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-2018-3720/ (Markdown: https://insights.sbomify.com/CVE-2018-3720/index.md)","id":"CVE-2018-3720","markdown":"https://insights.sbomify.com/CVE-2018-3720/index.md","name":"CVE-2018-3720","record":{"aliases":["GHSA-xcvv-84j5-jw9h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js deep assign library","requires_auth":"low_privilege","summary":"A prototype pollution vulnerability in the assign-deep library allows attackers to modify Object prototypes, affecting all objects in the application.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"assign-deep","vendor":"assign-deep_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-471","name":"Modification of Assumed-Immutable Data (MAID)"}],"description":"assign-deep node module before 0.4.7 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","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 in assign-deep","id":"CVE-2018-3720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Prototype Pollution in lodash","id":"CVE-2018-3721"},"packages":[{"ecosystem":"npm","fixed":["0.4.7"],"introduced":["0"],"last_affected":[],"package":"assign-deep","purl":null,"source":"GHSA-xcvv-84j5-jw9h"},{"ecosystem":"npm","fixed":["0.4.7"],"introduced":["0"],"last_affected":[],"package":"assign-deep","purl":"pkg:npm/assign-deep","source":"GHSA-xcvv-84j5-jw9h"}],"prev":{"headline":"Prototype Pollution in mixin-deep","id":"CVE-2018-3719"},"products":["assign-deep node module"],"published":"2018-06-07","related":[{"cvss_score":7.5,"headline":"assign-deep Vulnerable to Prototype Pollution","id":"CVE-2019-10745","kev_date_added":null,"published":"2019-08-20"}],"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":["HackerOne"]},"summary":"A prototype pollution vulnerability in the assign-deep library allows attackers to modify Object prototypes, affecting all objects in the application.","url":"https://insights.sbomify.com/CVE-2018-3720/"}