Application property manipulation via constructor payload
Published Jun 2, 2021 · Updated Aug 3, 2024
Prototype pollution in merge-deep before 3.0.3 allows attackers to modify inherited application properties via crafted objects. The recursive merge accepts a constructor key and descends into its prototype member, allowing attacker-controlled values to mutate Object.prototype even though proto is blocked. A consuming application must pass attacker-influenced objects to the library; effects depend on how inherited properties are used and range from authorization changes or service crashes to code execution.
Summary
What happened
Prototype pollution in merge-deep before 3.0.3 allows attackers to modify inherited application properties via crafted objects. The recursive merge accepts a constructor key and descends into its prototype member, allowing attacker-controlled values to mutate Object.prototype even though proto is blocked. A consuming application must pass attacker-influenced objects to the library; effects depend on how inherited properties are used and range from authorization changes or service crashes to code execution.
The record
- CVE
- CVE-2021-26707
- Published
- Jun 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Constructor payload 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