# CVE-2020-36618: Furqan node-whois index.coffee prototype pollution

> Prototype pollution in node-whois allows remote attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-97jv-c342-5xhc

## What is CVE-2020-36618?

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.

### Official 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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-36618?

2 open source packages ship an affected version, including whois. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `whois` | npm | All versions | 2.13.6 |
| `whois` | npm | All versions | 2.13.6 |

Products: Furqansofware Node Whois.

## How do I fix CVE-2020-36618?

Upgrade whois to 2.13.6 or later.

## Is CVE-2020-36618 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36618 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36618 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36618 exists.

Affected packages and fixed versions:
- whois (npm): affected all versions; fixed in 2.13.6
- whois (npm): affected all versions; fixed in 2.13.6

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36618/ (Markdown: https://insights.sbomify.com/CVE-2020-36618/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36618
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36618
- OSV: https://osv.dev/vulnerability/CVE-2020-36618

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36618/
Summaries are generated and may contain mistakes; the official description above is the record.