Disassembler crash via out-of-bounds stack read
Published Oct 3, 2022 · Updated Aug 3, 2024
Stack-buffer overflow in Ndisasm in NASM 2.16 allows context-dependent attackers to crash the disassembler via a crafted binary file. In disasm.c, do_ea reads one byte beyond a 64-byte stack buffer while matches parses attacker-controlled instruction data. Exploitation requires Ndisasm to process the file and interrupts only that process; no confidentiality or integrity impact is reported.
Summary
What happened
Stack-buffer overflow in Ndisasm in NASM 2.16 allows context-dependent attackers to crash the disassembler via a crafted binary file. In disasm.c, do_ea reads one byte beyond a 64-byte stack buffer while matches parses attacker-controlled instruction data. Exploitation requires Ndisasm to process the file and interrupts only that process; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2022-41420
- Published
- Oct 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 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
- Ndisasm stack_overflow.1 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