Assembler crash via unchecked debug type copy
Published Jan 4, 2023 · Updated Apr 10, 2025
Global buffer overflow in NASM 2.16 allows local users to crash the assembler by supplying crafted input for debug output. The dbgdbg_typevalue routine in output/outdbg.c copies an attacker-controlled debug type value into a global buffer without checking its length. Execution requires user interaction with crafted assembler input; the demonstrated consequence is a CLI crash, and Debian records no security impact.
Summary
What happened
Global buffer overflow in NASM 2.16 allows local users to crash the assembler by supplying crafted input for debug output. The dbgdbg_typevalue routine in output/outdbg.c copies an attacker-controlled debug type value into a global buffer without checking its length. Execution requires user interaction with crafted assembler input; the demonstrated consequence is a CLI crash, and Debian records no security impact.
The record
- CVE
- CVE-2022-46456
- Published
- Jan 4, 2023
- Updated
- Apr 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 4, 2023CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record 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.
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