Assembler crash via recursive expression parsing
Published Apr 24, 2023 · Updated Aug 2, 2024
Stack overflow in Yasm 1.3.0.55.g101bc allows local users to crash the assembler by supplying a crafted assembly source file. The parse_expr1 path repeatedly descends through the NASM expression-parser chain without bounding recursion, exhausting the process stack. Exploitation requires a user to invoke Yasm on the file, and the demonstrated consequence is termination of that process; the CVE remains disputed.
Summary
What happened
Stack overflow in Yasm 1.3.0.55.g101bc allows local users to crash the assembler by supplying a crafted assembly source file. The parse_expr1 path repeatedly descends through the NASM expression-parser chain without bounding recursion, exhausting the process stack. Exploitation requires a user to invoke Yasm on the file, and the demonstrated consequence is termination of that process; the CVE remains disputed.
The record
- CVE
- CVE-2023-29582
- Published
- Apr 24, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 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.
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
- parse_expr1 crashing inputproof 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