Assembler crash via null pointer dereference
Published Aug 22, 2023 · Updated Oct 3, 2024
NULL pointer dereference in NASM 2.16rc0 allows local users to crash the assembler during IEEE output generation in ieee_write_file. Published records identify the null dereference and function but do not disclose the triggering input or the missing check that permits it. The published CVSS assessment requires local access and user interaction; the consequence is limited to termination of the assembler process.
Summary
What happened
NULL pointer dereference in NASM 2.16rc0 allows local users to crash the assembler during IEEE output generation in ieee_write_file. Published records identify the null dereference and function but do not disclose the triggering input or the missing check that permits it. The published CVSS assessment requires local access and user interaction; the consequence is limited to termination of the assembler process.
The record
- CVE
- CVE-2023-38665
- Published
- Aug 22, 2023
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 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.
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