Assembler crash via interior allocation pointer
Published Aug 22, 2023 · Updated Oct 4, 2024
Use after free in NASM 2.14.02 allows local users to crash the assembler through a crafted NASM command that another user runs. In expand_one_smacro in asm/preproc.c, mempcpy advances the allocation pointer, and the code passes that interior pointer to set_text_free instead of the allocation's start. Execution requires local access and user interaction; the documented consequence is a crash of the NASM command-line process, not broader system compromise.
Summary
What happened
Use after free in NASM 2.14.02 allows local users to crash the assembler through a crafted NASM command that another user runs. In expand_one_smacro in asm/preproc.c, mempcpy advances the allocation pointer, and the code passes that interior pointer to set_text_free instead of the allocation's start. Execution requires local access and user interaction; the documented consequence is a crash of the NASM command-line process, not broader system compromise.
The record
- CVE
- CVE-2020-18780
- Published
- Aug 22, 2023
- Updated
- Oct 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 4, 2024Record 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
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