Assembler hang via preprocessor token-pasting loop
Published Dec 22, 2021 · Updated Aug 4, 2024
Infinite loop in NASM 2.16rc0 allows local users to hang the assembler by processing a crafted assembly source file. The gpaste_tokens function in the preprocessor enters a nonterminating loop while handling the crafted token sequence; the exact faulty branch is not publicly documented. Processing attacker-supplied source is required, and the documented consequence is limited to interruption of the assembler process.
Summary
What happened
Infinite loop in NASM 2.16rc0 allows local users to hang the assembler by processing a crafted assembly source file. The gpaste_tokens function in the preprocessor enters a nonterminating loop while handling the crafted token sequence; the exact faulty branch is not publicly documented. Processing attacker-supplied source is required, and the documented consequence is limited to interruption of the assembler process.
The record
- CVE
- CVE-2021-45257
- Published
- Dec 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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