Process crash via unbounded recursive backpropagation
Published Mar 29, 2022 · Updated Aug 3, 2024
Stack exhaustion in re2c 2.2 allows local users to crash the lexer generator by processing a crafted re2c specification. The re2c::backprop function in src/dfa/dead_rules.cc recursively re-enters itself without a safe depth bound until the process stack is exhausted. Reachability requires local invocation of the command-line tool on attacker-controlled input, and the demonstrated consequence is limited to termination of that process.
Summary
What happened
Stack exhaustion in re2c 2.2 allows local users to crash the lexer generator by processing a crafted re2c specification. The re2c::backprop function in src/dfa/dead_rules.cc recursively re-enters itself without a safe depth bound until the process stack is exhausted. Reachability requires local invocation of the command-line tool on attacker-controlled input, and the demonstrated consequence is limited to termination of that process.
The record
- CVE
- CVE-2022-23901
- Published
- Mar 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2022CVE 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?
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
- re2c backprop stack-overflow reproducer reportproof 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