Code execution via unsafe configuration property copying
Published Jul 1, 2024 · Updated Aug 2, 2024
Prototype pollution in RequireJS 2.3.6 and earlier allows remote attackers to execute code or interrupt an application via configuration objects. The configure path uses eachProp to copy attacker-controlled proto or constructor keys into internal objects instead of rejecting them. Exploitation requires an embedding application to pass attacker-controlled configuration data; code execution depends on a usable gadget.
Summary
What happened
Prototype pollution in RequireJS 2.3.6 and earlier allows remote attackers to execute code or interrupt an application via configuration objects. The configure path uses eachProp to copy attacker-controlled proto or constructor keys into internal objects instead of rejecting them. Exploitation requires an embedding application to pass attacker-controlled configuration data; code execution depends on a usable gadget.
The record
- CVE
- CVE-2024-38999
- Published
- Jul 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- RequireJS
- Product
- RequireJS
- Classifications
- CWE-1321, T1190
- 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=2.3.6
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
- RequireJS 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