Application logic manipulation via unsafe recursive object merge
Published Aug 29, 2024 · Updated Aug 29, 2024
Prototype pollution in Chartist 1.0 through 1.3.0 allows attackers to modify Object.prototype through a crafted extend argument. The extend function recursively copies attacker-supplied object keys without rejecting proto, so assignment reaches the shared Object prototype. Exploitation requires an application to pass untrusted objects to extend; polluted inherited properties can alter application logic, while further effects depend on available gadgets.
Summary
What happened
Prototype pollution in Chartist 1.0 through 1.3.0 allows attackers to modify Object.prototype through a crafted extend argument. The extend function recursively copies attacker-supplied object keys without rejecting proto, so assignment reaches the shared Object prototype. Exploitation requires an application to pass untrusted objects to extend; polluted inherited properties can alter application logic, while further effects depend on available gadgets.
The record
- CVE
- CVE-2024-45435
- Published
- Aug 29, 2024
- Updated
- Aug 29, 2024
- Vendor
- Chartist
- Product
- Chartist
- Classifications
- CWE-1321, CAPEC-1, CAPEC-180, CAPEC-77
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=1.0 <=1.3.0
What conditions does exploitation require?
What is affected?
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
- Chartist extend prototype-pollution 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