Process crash via uncontrolled fixed-tag recursion
Published Apr 29, 2020 · Updated Aug 5, 2024
Uncontrolled recursion in re2c before 2.0 allows local users to crash the process by supplying a crafted lexer specification. The find_fixed_tags routine recursively processes fixed-tag structures without a depth bound, consuming the process stack until it overflows. A user must cause re2c to process the input; the published reproduction used a 256 KB stack and ended in a segmentation-fault crash.
Summary
What happened
Uncontrolled recursion in re2c before 2.0 allows local users to crash the process by supplying a crafted lexer specification. The find_fixed_tags routine recursively processes fixed-tag structures without a depth bound, consuming the process stack until it overflows. A user must cause re2c to process the input; the published reproduction used a 256 KB stack and ended in a segmentation-fault crash.
The record
- CVE
- CVE-2018-21232
- Published
- Apr 29, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-674, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- overflow-1.re small-stack reproducerproof 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