Process crash via macro-parameter stack lifetime error
Published Aug 22, 2023 · Updated Oct 7, 2024
Stack-use-after-scope in NASM before 2.15.04 allows context-dependent attackers to crash the assembler via a crafted asm file. The expand_mmac_params function in asm/preproc.c uses a stack-backed object after its scope ends during macro-parameter expansion. Processing an attacker-supplied assembly file requires a user or build process to invoke NASM; successful triggering terminates that process.
Summary
What happened
Stack-use-after-scope in NASM before 2.15.04 allows context-dependent attackers to crash the assembler via a crafted asm file. The expand_mmac_params function in asm/preproc.c uses a stack-backed object after its scope ends during macro-parameter expansion. Processing an attacker-supplied assembly file requires a user or build process to invoke NASM; successful triggering terminates that process.
The record
- CVE
- CVE-2020-21686
- Published
- Aug 22, 2023
- Updated
- Oct 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-562, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 7, 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