Process crash via repeated stream deallocation
Published Jan 14, 2022 · Updated Aug 4, 2024
Use-after-free in Modex 2.11 allows context-dependent attackers to crash the process via a crafted C source file. The process_input path passes an already freed stream to Fclose again, causing glibc to detect a double free in its tcache. A victim must run Modex on the crafted input; the demonstrated impact is process abort, with no reported code execution or data exposure.
Summary
What happened
Use-after-free in Modex 2.11 allows context-dependent attackers to crash the process via a crafted C source file. The process_input path passes an already freed stream to Fclose again, causing glibc to detect a double free in its tcache. A victim must run Modex on the crafted input; the demonstrated impact is process abort, with no reported code execution or data exposure.
The record
- CVE
- CVE-2021-46169
- Published
- Jan 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2022CVE 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
- Modex 2.11 crafted C source proof of conceptproof 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