Assembler crash via null pointer dereference
Published Mar 29, 2023 · Updated Feb 18, 2025
Null pointer dereference in NASM 2.16 allows local users to crash the assembler by causing it to process a crafted input file. The obj_directive routine in output/outobj.c dereferences a null pointer while handling malformed object-output directives; public material does not identify the exact field or state that becomes null. Exploitation requires a user or build process to invoke the command-line tool on attacker-controlled source, and the bounded consequence is termination of that NASM process.
Summary
What happened
Null pointer dereference in NASM 2.16 allows local users to crash the assembler by causing it to process a crafted input file. The obj_directive routine in output/outobj.c dereferences a null pointer while handling malformed object-output directives; public material does not identify the exact field or state that becomes null. Exploitation requires a user or build process to invoke the command-line tool on attacker-controlled source, and the bounded consequence is termination of that NASM process.
The record
- CVE
- CVE-2022-44368
- Published
- Mar 29, 2023
- Updated
- Feb 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2023CVE publishedPublication date reported by the CVE source.
- Feb 18, 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.
Public exploit references
- NASM Bugzilla 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