Assembler crash via null pointer dereference
Published Jul 26, 2023 · Updated Oct 23, 2024
NULL pointer dereference in Yasm 1.3.0.78 allows local users to crash the assembler by processing a crafted assembly file. During ELF32 symbol-table output, elf_symtab_write_to_file calls yasm_intnum_copy, which reads through a null pointer in intnum.c. Exploitation requires Yasm to process attacker-controlled input with the affected ELF32 path and terminates only the assembler process.
Summary
What happened
NULL pointer dereference in Yasm 1.3.0.78 allows local users to crash the assembler by processing a crafted assembly file. During ELF32 symbol-table output, elf_symtab_write_to_file calls yasm_intnum_copy, which reads through a null pointer in intnum.c. Exploitation requires Yasm to process attacker-controlled input with the affected ELF32 path and terminates only the assembler process.
The record
- CVE
- CVE-2023-37732
- Published
- Jul 26, 2023
- Updated
- Oct 23, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2023CVE publishedPublication date reported by the CVE source.
- Oct 23, 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
- Yasm ELF32 crafted-file proof of conceptproof 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