Assembler crash via out-of-bounds expression read
Published Jan 2, 2024 · Updated Jun 3, 2025
Heap buffer overflow in Yasm 1.3.0.86.g9def allows context-dependent attackers to crash the assembler with a crafted input file. The expr_delete_term function reads a four-byte term field immediately beyond a 56-byte heap allocation while simplifying the crafted expression tree. A user must invoke Yasm on the file; the demonstrated consequence is a process crash, with no shown confidentiality or integrity impact.
Summary
What happened
Heap buffer overflow in Yasm 1.3.0.86.g9def allows context-dependent attackers to crash the assembler with a crafted input file. The expr_delete_term function reads a four-byte term field immediately beyond a 56-byte heap allocation while simplifying the crafted expression tree. A user must invoke Yasm on the file; the demonstrated consequence is a process crash, with no shown confidentiality or integrity impact.
The record
- CVE
- CVE-2023-49556
- Published
- Jan 2, 2024
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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
- poc.zip crafted Yasm 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