Application crash via malformed macro expansion
Published May 17, 2023 · Updated Jan 22, 2025
Heap buffer overflow in NASM 2.16.02rc1 allows local users to crash the assembler by opening a crafted assembly source file. The expand_mmacro() function in asm/preproc.c writes beyond an allocated heap buffer while expanding malformed macro input. A user must invoke NASM on the crafted file; the documented consequence is process termination, with no established code-execution impact.
Summary
What happened
Heap buffer overflow in NASM 2.16.02rc1 allows local users to crash the assembler by opening a crafted assembly source file. The expand_mmacro() function in asm/preproc.c writes beyond an allocated heap buffer while expanding malformed macro input. A user must invoke NASM on the crafted file; the documented consequence is process termination, with no established code-execution impact.
The record
- CVE
- CVE-2023-31722
- Published
- May 17, 2023
- Updated
- Jan 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, 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
No public exploit references are available in this record.
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