Service crash via Object.prototype pollution
Published Mar 16, 2021 · Updated Apr 30, 2025
Prototype pollution in Patchmerge 1.0.0 through 1.0.1 allows attackers to corrupt inherited object properties via crafted JSON merge patches. The objectMerge recursion follows a proto property into Object.prototype and writes attacker-controlled names and values there instead of creating an own object. An application must pass attacker-controlled patch data to the library; the resulting process-wide property changes crash the service or, when a suitable gadget exists, enable code execution.
Summary
What happened
Prototype pollution in Patchmerge 1.0.0 through 1.0.1 allows attackers to corrupt inherited object properties via crafted JSON merge patches. The objectMerge recursion follows a proto property into Object.prototype and writes attacker-controlled names and values there instead of creating an own object. An application must pass attacker-controlled patch data to the library; the resulting process-wide property changes crash the service or, when a suitable gadget exists, enable code execution.
The record
- CVE
- CVE-2021-25916
- Published
- Mar 16, 2021
- Updated
- Apr 30, 2025
- Vendor
- Paul Humphreys
- Product
- Patchmerge
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2021CVE publishedPublication date reported by the CVE source.
- Apr 30, 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=1.0.0, 1.0.1
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
- Object.prototype pollution demonstration in test2.jsproof 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