Assembler crash via out-of-bounds IEEE writer read
Published Jan 4, 2023 · Updated Apr 10, 2025
Out-of-bounds read in NASM 2.16 allows local users to crash the assembler by processing a crafted file with IEEE output enabled. The ieee_write_file routine in output/outieee.c performs an invalid memory read while finalizing IEEE-695 output, triggering a segmentation violation. Exploitation requires a user or automated build process to invoke NASM on attacker-controlled assembly input with the IEEE output format, and the observed consequence is termination of that NASM process.
Summary
What happened
Out-of-bounds read in NASM 2.16 allows local users to crash the assembler by processing a crafted file with IEEE output enabled. The ieee_write_file routine in output/outieee.c performs an invalid memory read while finalizing IEEE-695 output, triggering a segmentation violation. Exploitation requires a user or automated build process to invoke NASM on attacker-controlled assembly input with the IEEE output format, and the observed consequence is termination of that NASM process.
The record
- CVE
- CVE-2022-46457
- Published
- Jan 4, 2023
- Updated
- Apr 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
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
- NASM ieee_write_file crash 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