Assembly interruption via out-of-bounds dot-label read
Published Apr 25, 2023 · Updated Aug 2, 2024
Heap-buffer over-read in Yasm 1.3.0 allows local users to crash the assembler by supplying a crafted NASM-syntax source file. The handle_dot_label lexer duplicates a three-byte dot-label token and then reads one byte immediately beyond the allocated heap region. Reachability requires Yasm to process attacker-controlled assembly source; the upstream project treats such input as trusted and disputes any security consequence.
Summary
What happened
Heap-buffer over-read in Yasm 1.3.0 allows local users to crash the assembler by supplying a crafted NASM-syntax source file. The handle_dot_label lexer duplicates a three-byte dot-label token and then reads one byte immediately beyond the allocated heap region. Reachability requires Yasm to process attacker-controlled assembly source; the upstream project treats such input as trusted and disputes any security consequence.
The record
- CVE
- CVE-2023-30402
- Published
- Apr 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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
- 137-HOF Yasm 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