Prototype pollution via unsafe setObject path
Published Dec 17, 2021 · Updated Sep 16, 2024
Prototype Pollution in OpenJS Foundation Dojo Toolkit before 1.17.0 allows remote attackers to alter JavaScript object prototypes via crafted input. The setObject function resolves attacker-controlled property paths without blocking prototype-linked keys, allowing writes into shared prototypes. When an application passes untrusted paths to this function, polluted properties propagate to other objects and can enable arbitrary code execution or service interruption.
Summary
What happened
Prototype Pollution in OpenJS Foundation Dojo Toolkit before 1.17.0 allows remote attackers to alter JavaScript object prototypes via crafted input. The setObject function resolves attacker-controlled property paths without blocking prototype-linked keys, allowing writes into shared prototypes. When an application passes untrusted paths to this function, polluted properties propagate to other objects and can enable arbitrary code execution or service interruption.
The record
- CVE
- CVE-2021-23450
- Published
- Dec 17, 2021
- Updated
- Sep 16, 2024
- Vendor
- OpenJS Foundation
- Product
- Dojo Toolkit
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 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
- Dojo setObject prototype-pollution proof of conceptproof of concept · unverified
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