Assembler crash via null read in expand_smacro
Published Jan 2, 2024 · Updated Jun 17, 2025
A null-pointer dereference in YASM 1.3.0.86.g9def allows local users to crash the assembler via crafted assembly source. The expand_smacro function in modules/preprocs/nasm/nasm-pp.c reads through a null pointer while expanding malformed single-line macro input. Exploitation requires a user or build process to run YASM on the crafted file and interrupts only that assembler process; no confidentiality or integrity impact is reported.
Summary
What happened
A null-pointer dereference in YASM 1.3.0.86.g9def allows local users to crash the assembler via crafted assembly source. The expand_smacro function in modules/preprocs/nasm/nasm-pp.c reads through a null pointer while expanding malformed single-line macro input. Exploitation requires a user or build process to run YASM on the crafted file and interrupts only that assembler process; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2023-49555
- Published
- Jan 2, 2024
- Updated
- Jun 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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
- expand_smacro crash poc.zipproof 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