Process crash via unchecked Xasc operand
Published Feb 27, 2023 · Updated Mar 11, 2025
NULL pointer dereference in crasm 1.8-3 allows local users to crash the command-line assembler by supplying a crafted source file. The Xasc function assigns its unchecked oper argument to s and immediately dereferences s to read a delimiter, even when asmline passes a NULL operand. Exploitation requires the crafted file to be passed to the local CLI and terminates only that crasm process with a segmentation fault.
Summary
What happened
NULL pointer dereference in crasm 1.8-3 allows local users to crash the command-line assembler by supplying a crafted source file. The Xasc function assigns its unchecked oper argument to s and immediately dereferences s to read a delimiter, even when asmline passes a NULL operand. Exploitation requires the crafted file to be passed to the local CLI and terminates only that crasm process with a segmentation fault.
The record
- CVE
- CVE-2023-23108
- Published
- Feb 27, 2023
- Updated
- Mar 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 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.
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
- crasm-fuzz NULL pointer reproducerproof 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