Code execution via prototype-polluting object assignment
Published Jul 1, 2024 · Updated Aug 2, 2024
Prototype pollution in @c3/utils-1 1.0.131 allows remote attackers to execute code or interrupt service via crafted object keys. The assign and set helpers accept proto in object or path input and write attacker-chosen properties onto Object.prototype. No authentication is required, but code execution or a crash depends on a suitable application gadget that consumes a polluted property.
Summary
What happened
Prototype pollution in @c3/utils-1 1.0.131 allows remote attackers to execute code or interrupt service via crafted object keys. The assign and set helpers accept proto in object or path input and write attacker-chosen properties onto Object.prototype. No authentication is required, but code execution or a crash depends on a suitable application gadget that consumes a polluted property.
The record
- CVE
- CVE-2024-39016
- Published
- Jul 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- @c3/utils-1 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