Prototype pollution via unsafe recursive merge
Published Jun 17, 2021 · Updated Sep 16, 2024
Prototype pollution in all lutils versions allows attackers to modify Object.prototype properties through crafted merge inputs. The main merge function recursively copies attacker-controlled proto keys into a destination object without filtering prototype-mutating properties. A consuming application must pass attacker-controlled objects to merge; the resulting inherited properties can alter application behavior, while downstream impact depends on available code paths.
Summary
What happened
Prototype pollution in all lutils versions allows attackers to modify Object.prototype properties through crafted merge inputs. The main merge function recursively copies attacker-controlled proto keys into a destination object without filtering prototype-mutating properties. A consuming application must pass attacker-controlled objects to merge; the resulting inherited properties can alter application behavior, while downstream impact depends on available code paths.
The record
- CVE
- CVE-2021-23396
- Published
- Jun 17, 2021
- Updated
- Sep 16, 2024
- Vendor
- Lutils Project
- Product
- lutils
- Classifications
- CWE-1321, CAPEC-1, CAPEC-180, CAPEC-77
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 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?
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
- Snyk lutils merge 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