Code execution via unsafe property path assignment
Published Jul 1, 2024 · Updated Aug 2, 2024
Prototype pollution in setValue in amoyjs @amoy/common 1.0.10 allows remote attackers to alter inherited object properties. The path setter follows an attacker-controlled proto key and assigns the supplied value on Object.prototype instead of confining it to the destination object. Reachability requires a consuming application to pass attacker-controlled property paths to setValue; code execution or a service crash depends on a downstream gadget, and the supplier disputes the report because the library does not call the function.
Summary
What happened
Prototype pollution in setValue in amoyjs @amoy/common 1.0.10 allows remote attackers to alter inherited object properties. The path setter follows an attacker-controlled proto key and assigns the supplied value on Object.prototype instead of confining it to the destination object. Reachability requires a consuming application to pass attacker-controlled property paths to setValue; code execution or a service crash depends on a downstream gadget, and the supplier disputes the report because the library does not call the function.
The record
- CVE
- CVE-2024-39003
- Published
- Jul 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- amoyjs
- Product
- @amoy/common
- 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.10
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
- @amoy/common 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