Process crash via uncounted prefix combinator depth
Published Aug 19, 2024 · Updated Sep 13, 2024
Stack exhaustion in Rust Bitcoin Miniscript before 12.2.0 allows remote attackers to crash consuming applications via crafted input. The string parser fails to count prefix combinators such as n: toward MAX_RECURSION_DEPTH, builds an excessively deep tree, and later recursive operations exhaust the stack. Exploitation requires a consuming application to parse attacker-controlled Miniscript text or Script data; the bounded consequence is a process crash.
Summary
What happened
Stack exhaustion in Rust Bitcoin Miniscript before 12.2.0 allows remote attackers to crash consuming applications via crafted input. The string parser fails to count prefix combinators such as n: toward MAX_RECURSION_DEPTH, builds an excessively deep tree, and later recursive operations exhaust the stack. Exploitation requires a consuming application to parse attacker-controlled Miniscript text or Script data; the bounded consequence is a process crash.
The record
- CVE
- CVE-2024-44073
- Published
- Aug 19, 2024
- Updated
- Sep 13, 2024
- Vendor
- Rust Bitcoin
- Product
- Miniscript
- Classifications
- CWE-674, CWE-787, CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 13, 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 <12.2.0
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
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