Application crash via unbounded nested-array recursion
Published May 26, 2022 · Updated Aug 4, 2024
Stack exhaustion in tinytoml 0.4 allows attackers to crash a consuming application by supplying a crafted TOML file. The parseFile path reaches Parser::parseArray and Parser::parseValue, which recursively call each other for nested arrays without a depth limit until the process stack is exhausted. The application must parse attacker-controlled input, and user interaction is required; successful exploitation interrupts only the consuming process.
Summary
What happened
Stack exhaustion in tinytoml 0.4 allows attackers to crash a consuming application by supplying a crafted TOML file. The parseFile path reaches Parser::parseArray and Parser::parseValue, which recursively call each other for nested arrays without a depth limit until the process stack is exhausted. The application must parse attacker-controlled input, and user interaction is required; successful exploitation interrupts only the consuming process.
The record
- CVE
- CVE-2021-42692
- Published
- May 26, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- tinytoml parseFile crash testcaseproof 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