Assembler crash via crafted source file
Published Aug 22, 2023 · Updated Oct 7, 2024
Buffer overflow in NASM 2.15rc0 allows local users to crash the assembler by supplying a crafted assembly source file. The published record identifies hash_findi in hashtbl.c but does not disclose which bounds check or memory operation is defective. Another user must process the supplied file, and both upstream and Ubuntu were unable to reproduce the reported crash.
Summary
What happened
Buffer overflow in NASM 2.15rc0 allows local users to crash the assembler by supplying a crafted assembly source file. The published record identifies hash_findi in hashtbl.c but does not disclose which bounds check or memory operation is defective. Another user must process the supplied file, and both upstream and Ubuntu were unable to reproduce the reported crash.
The record
- CVE
- CVE-2020-21685
- Published
- Aug 22, 2023
- Updated
- Oct 7, 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 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
- Crafted assembly file proof of conceptproof of concept · unverified
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