{"answers":{"affected":"4 open source packages ship an affected version, including node.extend. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16491 in the wild and no public exploit code.","fix":"Upgrade node.extend to a fixed version for your release line: 1.1.7 or 2.0.1.","what":"CVE-2018-16491 is a critical code injection vulnerability in HackerOne node.extend, published on 1 Feb 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-2018-16491 and fix it if it is affected.\n\nWhat it is: CVE-2018-16491 is a critical code injection vulnerability in HackerOne node.extend, published on 1 Feb 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-2018-16491 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node.extend (npm): affected all versions; fixed in 1.1.7\n- node.extend (npm): affected all versions; fixed in 1.1.7\n- node.extend (npm): affected from 2.0.0; fixed in 2.0.1\n- node.extend (npm): affected from 2.0.0; fixed in 2.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-2018-16491/ (Markdown: https://insights.sbomify.com/CVE-2018-16491/index.md)","id":"CVE-2018-16491","markdown":"https://insights.sbomify.com/CVE-2018-16491/index.md","name":"CVE-2018-16491","record":{"aliases":["DEBIAN-CVE-2018-16491","GHSA-r96c-57pf-9jjm","UBUNTU-CVE-2018-16491"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js extend library","requires_auth":"none","summary":"Prototype pollution in node.extend allows attackers to inject properties into Object.prototype, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node.extend","vendor":"dreamerslab"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"A prototype pollution vulnerability was found in node.extend \u003c1.1.7, ~\u003c2.0.1 that allows an attacker to inject arbitrary properties onto Object.prototype.","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 node.extend","id":"CVE-2018-16491","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":4,"n_references":1,"next":{"headline":"Prototype Pollution in extend","id":"CVE-2018-16492"},"packages":[{"ecosystem":"npm","fixed":["1.1.7"],"introduced":["0"],"last_affected":[],"package":"node.extend","purl":null,"source":"GHSA-r96c-57pf-9jjm"},{"ecosystem":"npm","fixed":["1.1.7"],"introduced":["0"],"last_affected":[],"package":"node.extend","purl":"pkg:npm/node.extend","source":"GHSA-r96c-57pf-9jjm"},{"ecosystem":"npm","fixed":["2.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"node.extend","purl":null,"source":"GHSA-r96c-57pf-9jjm"},{"ecosystem":"npm","fixed":["2.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"node.extend","purl":"pkg:npm/node.extend","source":"GHSA-r96c-57pf-9jjm"}],"prev":{"headline":"Prototype Pollution in mpath","id":"CVE-2018-16490"},"products":["node.extend"],"published":"2019-02-01","related":[],"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-05","vendors":["HackerOne"]},"summary":"Prototype pollution in node.extend allows attackers to inject properties into Object.prototype, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2018-16491/"}