{"answers":{"affected":"2 open source packages ship an affected version, including whois. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36618 exists.","fix":"Upgrade whois to 2.13.6 or later.","what":"CVE-2020-36618 is a medium-severity vulnerability in Furqan node-whois, published on 19 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-36618 and fix it if it is affected.\n\nWhat it is: CVE-2020-36618 is a medium-severity vulnerability in Furqan node-whois, published on 19 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36618 exists.\n\nAffected packages and fixed versions:\n- whois (npm): affected all versions; fixed in 2.13.6\n- whois (npm): affected all versions; fixed in 2.13.6\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-36618/ (Markdown: https://insights.sbomify.com/CVE-2020-36618/index.md)","id":"CVE-2020-36618","markdown":"https://insights.sbomify.com/CVE-2020-36618/index.md","name":"CVE-2020-36618","record":{"aliases":["GHSA-97jv-c342-5xhc"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js whois library","requires_auth":"low_privilege","summary":"Prototype pollution in node-whois allows remote attackers to modify 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":"VulDB","cpe":[{"product":"node_whois","vendor":"furqansofware"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability classified as critical has been found in Furqan node-whois. Affected is an unknown function of the file index.coffee. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). It is possible to launch the attack remotely. The name of the patch is 46ccc2aee8d063c7b6b4dee2c2834113b7286076. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-216252.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Furqan node-whois index.coffee prototype pollution","id":"CVE-2020-36618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"multimon-ng demod_flex.c add_ch format string","id":"CVE-2020-36619"},"packages":[{"ecosystem":"npm","fixed":["2.13.6"],"introduced":["0"],"last_affected":[],"package":"whois","purl":null,"source":"GHSA-97jv-c342-5xhc"},{"ecosystem":"npm","fixed":["2.13.6"],"introduced":["0"],"last_affected":[],"package":"whois","purl":"pkg:npm/whois","source":"GHSA-97jv-c342-5xhc"}],"prev":{"headline":"ewxrjk sftpserver parse.c sftp_parse_path uninitialized pointer","id":"CVE-2020-36617"},"products":["node-whois"],"published":"2022-12-19","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["Furqan"]},"summary":"Prototype pollution in node-whois allows remote attackers to modify object prototypes, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2020-36618/"}