Memory corruption via stale demangler array state
Published Nov 18, 2021 · Updated Aug 4, 2024
Use-after-free in GNU c++filt 2.26 allows context-dependent attackers to corrupt memory via crafted C++ symbols. In cplus-dem.c, squangle_mop_up frees btypevec and ktypevec but leaves their size fields nonzero, so later demangling writes through invalid storage. Exploitation requires a victim to process attacker-crafted input with c++filt; vendor assessments bound the consequence to memory disclosure, a utility crash, or code execution.
Summary
What happened
Use-after-free in GNU c++filt 2.26 allows context-dependent attackers to corrupt memory via crafted C++ symbols. In cplus-dem.c, squangle_mop_up frees btypevec and ktypevec but leaves their size fields nonzero, so later demangling writes through invalid storage. Exploitation requires a victim to process attacker-crafted input with c++filt; vendor assessments bound the consequence to memory disclosure, a utility crash, or code execution.
The record
- CVE
- CVE-2021-37322
- Published
- Nov 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- GCC Bug 99188 c++filt 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