Assembler crash via backslash counter underrun
Published Mar 29, 2023 · Updated Aug 3, 2024
Heap buffer overflow in quote_for_pmake in NASM before 2.16 and 2.16rc1 allows local users to crash the assembler with a crafted file. The function uses a post-decrement loop that leaves its backslash counter at -1, then reuses that value as a write count and overruns the allocated heap buffer. Exploitation requires a user to invoke NASM on attacker-controlled assembly input; the upstream report demonstrates a segmentation fault.
Summary
What happened
Heap buffer overflow in quote_for_pmake in NASM before 2.16 and 2.16rc1 allows local users to crash the assembler with a crafted file. The function uses a post-decrement loop that leaves its backslash counter at -1, then reuses that value as a write count and overruns the allocated heap buffer. Exploitation requires a user to invoke NASM on attacker-controlled assembly input; the upstream report demonstrates a segmentation fault.
The record
- CVE
- CVE-2022-44370
- Published
- Mar 29, 2023
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2023CVE publishedPublication date reported by the CVE source.
- Aug 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.
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 3392815 crash 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