Assembler crash via scanner out-of-bounds write
Published Aug 22, 2023 · Updated Oct 3, 2024
Out-of-bounds write in NASM 2.15rc0 allows attackers to crash the assembler by passing a crafted assembly file to its scanner. The scan function in stdscan.c writes beyond a buffer while processing the crafted assembly text, terminating the command-line process. A user or automated workflow must cause the local NASM executable to process the file; the documented consequence is a crash, not code execution.
Summary
What happened
Out-of-bounds write in NASM 2.15rc0 allows attackers to crash the assembler by passing a crafted assembly file to its scanner. The scan function in stdscan.c writes beyond a buffer while processing the crafted assembly text, terminating the command-line process. A user or automated workflow must cause the local NASM executable to process the file; the documented consequence is a crash, not code execution.
The record
- CVE
- CVE-2020-21687
- Published
- Aug 22, 2023
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 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.
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