Assembler crash via preprocessor use-after-free
Published Jul 26, 2022 · Updated Aug 3, 2024
Use-after-free in Yasm 1.3.0's NASM preprocessor allows local users to crash the assembler by processing a crafted source file. The pp_getline() function frees a heap allocation and subsequently reads four bytes from it while processing the crafted input. Exploitation requires Yasm to process the file; the demonstrated consequence is process termination, not code execution.
Summary
What happened
Use-after-free in Yasm 1.3.0's NASM preprocessor allows local users to crash the assembler by processing a crafted source file. The pp_getline() function frees a heap allocation and subsequently reads four bytes from it while processing the crafted input. Exploitation requires Yasm to process the file; the demonstrated consequence is process termination, not code execution.
The record
- CVE
- CVE-2021-33467
- Published
- Jul 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- yasm-5020-pp_getline-UAF 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