Assembler crash via null section dereference
Published Jan 2, 2024 · Updated Jun 18, 2025
NULL-pointer dereference in Yasm 1.3.0.86.g9def allows local users to crash the assembler by processing a crafted input file. During NASM expression parsing, parse_expr6 passes a null section pointer to yasm_section_bcs_first, which dereferences sect->bcs without validating the pointer. The user must run Yasm on the crafted file; the crash terminates that assembler process, and the project disputes any security consequence because it treats assembly inputs as trusted.
Summary
What happened
NULL-pointer dereference in Yasm 1.3.0.86.g9def allows local users to crash the assembler by processing a crafted input file. During NASM expression parsing, parse_expr6 passes a null section pointer to yasm_section_bcs_first, which dereferences sect->bcs without validating the pointer. The user must run Yasm on the crafted file; the crash terminates that assembler process, and the project disputes any security consequence because it treats assembly inputs as trusted.
The record
- CVE
- CVE-2023-49557
- Published
- Jan 2, 2024
- Updated
- Jun 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1203
- 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Crafted Yasm input 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