Object prototype modification via __proto__ lookup
Published Dec 19, 2022 · Updated Apr 15, 2025
Prototype pollution in Furqan Software Node WHOIS before 2.13.6 allows remote attackers to modify object prototypes via a crafted lookup. The lookup function in index.coffee uses the supplied address as a servers object key, so proto resolves the inherited prototype and defaults port and query properties onto it. Reachability requires a consuming application to pass an attacker-controlled address to lookup; the write corrupts shared object behavior in that Node.js process.
Summary
What happened
Prototype pollution in Furqan Software Node WHOIS before 2.13.6 allows remote attackers to modify object prototypes via a crafted lookup. The lookup function in index.coffee uses the supplied address as a servers object key, so proto resolves the inherited prototype and defaults port and query properties onto it. Reachability requires a consuming application to pass an attacker-controlled address to lookup; the write corrupts shared object behavior in that Node.js process.
The record
- CVE
- CVE-2020-36618
- Published
- Dec 19, 2022
- Updated
- Apr 15, 2025
- Vendor
- Furqan Software
- Product
- Node WHOIS
- Classifications
- CWE-74
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream __proto__ lookup proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo