Process crash via unbounded Rust demangling recursion
Published Jun 2, 2021 · Updated Aug 3, 2024
Uncontrolled recursion in GNU Binutils 2.36 and earlier allows attackers to crash a consuming process with a crafted Rust symbol. The demangle_path and demangle_type routines in libiberty/rust-demangle.c recursively parse nested symbol constructs without enforcing a depth limit, exhausting stack memory. Reachability requires a Binutils utility or linked consumer to demangle attacker-controlled symbol data; the documented result is a process crash, with no reported data disclosure or modification.
Summary
What happened
Uncontrolled recursion in GNU Binutils 2.36 and earlier allows attackers to crash a consuming process with a crafted Rust symbol. The demangle_path and demangle_type routines in libiberty/rust-demangle.c recursively parse nested symbol constructs without enforcing a depth limit, exhausting stack memory. Reachability requires a Binutils utility or linked consumer to demangle attacker-controlled symbol data; the documented result is a process crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-3530
- Published
- Jun 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-674, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=GNU Binutils version before and including 2.36
What conditions does exploitation require?
What is affected?
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