Prototype pollution via unsafe final-key assignment
Published Feb 8, 2021 · Updated Aug 3, 2024
Prototype pollution in Dynamoose 2.0.0 through 2.6.0 allows remote attackers to inject special object properties via crafted keys. The lib/utils/object/set.ts utility assigned values to final proto or constructor keys without rejecting those special property names. Exposure requires consuming code to pass attacker-controlled keys into the utility, resulting in inherited-property injection that alters downstream application behavior.
Summary
What happened
Prototype pollution in Dynamoose 2.0.0 through 2.6.0 allows remote attackers to inject special object properties via crafted keys. The lib/utils/object/set.ts utility assigned values to final proto or constructor keys without rejecting those special property names. Exposure requires consuming code to pass attacker-controlled keys into the utility, resulting in inherited-property injection that alters downstream application behavior.
The record
- CVE
- CVE-2021-21304
- Published
- Feb 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Dynamoose
- Product
- Dynamoose
- Classifications
- CWE-1321, CWE-915
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.0, < 2.7.0
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
No public exploit references are available in this record.
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