Code execution via unsafe prototype path traversal
Published Feb 2, 2021 · Updated Aug 3, 2024
Prototype pollution in dotty 0.0.1 through 0.1.0 allows remote attackers to crash services or execute code via crafted paths. The put function recursively follows dot-separated path components and writes through the inherited proto property without rejecting it. Applications are exposed when attacker-controlled paths reach put; process-wide prototype changes cause a crash or code execution when a usable downstream gadget exists.
Summary
What happened
Prototype pollution in dotty 0.0.1 through 0.1.0 allows remote attackers to crash services or execute code via crafted paths. The put function recursively follows dot-separated path components and writes through the inherited proto property without rejecting it. Applications are exposed when attacker-controlled paths reach put; process-wide prototype changes cause a crash or code execution when a usable downstream gadget exists.
The record
- CVE
- CVE-2021-25912
- Published
- Feb 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Deoxxa Development
- Product
- dotty
- Classifications
- CWE-1321, CAPEC-1, CAPEC-180, CAPEC-77
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=0.0.1, 0.0.2, 0.1.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
- Upstream prototype-pollution regression triggerproof 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