Process crash or code execution via prototype pollution
Published May 25, 2021 · Updated Aug 3, 2024
Prototype pollution in Rob Loach nconf-toml 0.0.1 through 0.0.2 allows attackers to corrupt the Node.js object prototype via crafted TOML input. The package exports its toml dependency's parse function directly, so attacker-controlled special property keys reach the dependency without filtering by the plugin. Exploitation requires a consuming application to parse attacker-controlled TOML; a polluted prototype can crash the process, while code execution depends on a compatible application gadget.
Summary
What happened
Prototype pollution in Rob Loach nconf-toml 0.0.1 through 0.0.2 allows attackers to corrupt the Node.js object prototype via crafted TOML input. The package exports its toml dependency's parse function directly, so attacker-controlled special property keys reach the dependency without filtering by the plugin. Exploitation requires a consuming application to parse attacker-controlled TOML; a polluted prototype can crash the process, while code execution depends on a compatible application gadget.
The record
- CVE
- CVE-2021-25946
- Published
- May 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Rob Loach
- Product
- nconf-toml
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 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
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
No public exploit references are available in this record.
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