Assembler crash via freed macro object dereference
Published Jan 2, 2024 · Updated Jun 18, 2025
Use-after-free in YASM 1.3.0.86.g9def allows context-dependent attackers to crash the assembler with a crafted source file. In do_directive, pp_getline frees a macro object before do_directive reads four bytes from that freed heap allocation. Processing the file is required, and the demonstrated result is an AddressSanitizer abort that interrupts the local assembly process.
Summary
What happened
Use-after-free in YASM 1.3.0.86.g9def allows context-dependent attackers to crash the assembler with a crafted source file. In do_directive, pp_getline frees a macro object before do_directive reads four bytes from that freed heap allocation. Processing the file is required, and the demonstrated result is an AddressSanitizer abort that interrupts the local assembly process.
The record
- CVE
- CVE-2023-49554
- Published
- Jan 2, 2024
- Updated
- Jun 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Jun 18, 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.
Weakness, pattern, technique
Public exploit references
- YASM do_directive use-after-free 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