Prototype pollution via unsafe __proto__ merge
Published Oct 20, 2021 · Updated Sep 16, 2024
Prototype pollution in x-assign 0.1.4 and earlier allows attackers to modify Object.prototype through an untrusted merge source. The assign routine recursively merges an enumerable proto property into the destination without blocking the special key, allowing nested properties to reach the global prototype. Applications must pass attacker-controlled object keys into the library; polluted inherited values can corrupt logic, crash the process, or enable application-specific code execution.
Summary
What happened
Prototype pollution in x-assign 0.1.4 and earlier allows attackers to modify Object.prototype through an untrusted merge source. The assign routine recursively merges an enumerable proto property into the destination without blocking the special key, allowing nested properties to reach the global prototype. Applications must pass attacker-controlled object keys into the library; polluted inherited values can corrupt logic, crash the process, or enable application-specific code execution.
The record
- CVE
- CVE-2021-23452
- Published
- Oct 20, 2021
- Updated
- Sep 16, 2024
- Vendor
- BinaryOps Software Inc.
- Product
- x-assign
- Classifications
- CWE-1321, CWE-915
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 20, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=0 <unspecified
What conditions does exploitation require?
What is affected?
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
- x-assign __proto__ proof of conceptproof of concept · unverified
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