Tool crash via unbounded Rust symbol recursion
Published Mar 26, 2022 · Updated Aug 3, 2024
Uncontrolled recursion in GNU GCC 11.2 allows local users to crash symbol-processing tools via a crafted Rust symbol. In libiberty/rust-demangle.c, demangle_const recursively follows constant back-references without limiting their depth, allowing crafted chains to consume the process stack. Exploitation requires a user to process attacker-controlled symbol data with an affected tool such as nm-new, and the bounded consequence is termination of that process.
Summary
What happened
Uncontrolled recursion in GNU GCC 11.2 allows local users to crash symbol-processing tools via a crafted Rust symbol. In libiberty/rust-demangle.c, demangle_const recursively follows constant back-references without limiting their depth, allowing crafted chains to consume the process stack. Exploitation requires a user to process attacker-controlled symbol data with an affected tool such as nm-new, and the bounded consequence is termination of that process.
The record
- CVE
- CVE-2022-27943
- Published
- Mar 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-674, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 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
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