Code execution and service interruption via prototype pollution
Published Jul 1, 2024 · Updated Aug 2, 2024
Prototype pollution in @akbr/patch-into 1.0.1 allows remote authenticated users to corrupt object prototypes through crafted patch paths. The patchInto function accepts a path containing proto and assigns an attacker-controlled value through that path, modifying Object.prototype for subsequently created objects. A consuming application must pass user-controlled paths into the library; resulting denial of service or code execution depends on an application-specific gadget.
Summary
What happened
Prototype pollution in @akbr/patch-into 1.0.1 allows remote authenticated users to corrupt object prototypes through crafted patch paths. The patchInto function accepts a path containing proto and assigns an attacker-controlled value through that path, modifying Object.prototype for subsequently created objects. A consuming application must pass user-controlled paths into the library; resulting denial of service or code execution depends on an application-specific gadget.
The record
- CVE
- CVE-2024-38991
- Published
- Jul 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- akbr
- Product
- @akbr/patch-into
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- authenticated
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.1
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
- Prototype pollution proof of concept for patchIntoproof 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