Object prototype modification via inherited property traversal
Published May 1, 2022 · Updated Sep 16, 2024
Prototype pollution in Dexie.js before 3.2.2 and 4.0.0-alpha.1 through 4.0.0-alpha.2 allows attackers to modify Object.prototype. The setByKeyPath function follows attacker-controlled key-path segments and, before the patch, reuses an inherited object because it checks only whether the lookup is truthy rather than whether the property belongs to the target object. Applications become exposed when they pass untrusted keys into collection modification or another reachable setByKeyPath call, allowing poisoned prototype properties to affect later application logic.
Summary
What happened
Prototype pollution in Dexie.js before 3.2.2 and 4.0.0-alpha.1 through 4.0.0-alpha.2 allows attackers to modify Object.prototype. The setByKeyPath function follows attacker-controlled key-path segments and, before the patch, reuses an inherited object because it checks only whether the lookup is truthy rather than whether the property belongs to the target object. Applications become exposed when they pass untrusted keys into collection modification or another reachable setByKeyPath call, allowing poisoned prototype properties to affect later application logic.
The record
- CVE
- CVE-2022-21189
- Published
- May 1, 2022
- Updated
- Sep 16, 2024
- Vendor
- Dexie
- Product
- Dexie.js
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2022CVE 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=4.0.0-alpha.1 <unspecified
- Affected versionversion=unspecified <3.2.2
- Affected versionversion=unspecified <4.0.0-alpha.3
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