Assembler crash via freed macro object read
Published May 17, 2023 · Updated Jan 22, 2025
Use-after-free in Yasm 1.3.0.55.g101bc allows context-dependent attackers to crash the assembler via a crafted source file. During NASM macro preprocessing, pp_getline frees a macro object through free_mmacro, but expand_mmac_params later reads eight bytes from that released heap allocation. The victim must run Yasm on the crafted file; the demonstrated outcome is process termination under AddressSanitizer, with no reported data exposure or code execution.
Summary
What happened
Use-after-free in Yasm 1.3.0.55.g101bc allows context-dependent attackers to crash the assembler via a crafted source file. During NASM macro preprocessing, pp_getline frees a macro object through free_mmacro, but expand_mmac_params later reads eight bytes from that released heap allocation. The victim must run Yasm on the crafted file; the demonstrated outcome is process termination under AddressSanitizer, with no reported data exposure or code execution.
The record
- CVE
- CVE-2023-31725
- Published
- May 17, 2023
- Updated
- Jan 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2023CVE publishedPublication date reported by the CVE source.
- Jan 22, 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 expand_mmac_params crashing inputproof 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