Assembler crash via stale macro pointer dereference
Published May 9, 2023 · Updated Jan 28, 2025
Use-after-free in Yasm 1.3.0 allows local users to crash the assembler by processing a crafted assembly source file. The NASM preprocessor frees a macro object in pp_getline, then the error function reads a field through the stale pointer, producing an AddressSanitizer abort. The trigger requires processing attacker-controlled source, and the Yasm project disputes security impact because its policy treats assembler inputs as trusted.
Summary
What happened
Use-after-free in Yasm 1.3.0 allows local users to crash the assembler by processing a crafted assembly source file. The NASM preprocessor frees a macro object in pp_getline, then the error function reads a field through the stale pointer, producing an AddressSanitizer abort. The trigger requires processing attacker-controlled source, and the Yasm project disputes security impact because its policy treats assembler inputs as trusted.
The record
- CVE
- CVE-2023-31974
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 2025Record 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
- Yasm 173-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