Assembler abort via freed-memory read
Published May 9, 2023 · Updated Jan 29, 2025
Use-after-free in Yasm 1.3.0 allows local users to abort assembly processing by supplying a crafted source file. While preprocessing the file, pp_getline frees an allocation through free_mmacro and later reads four bytes from inside that freed region. Exploitation requires Yasm to process the crafted input; the project expects inputs to be trusted and therefore disputes that the demonstrated process abort has a security consequence.
Summary
What happened
Use-after-free in Yasm 1.3.0 allows local users to abort assembly processing by supplying a crafted source file. While preprocessing the file, pp_getline frees an allocation through free_mmacro and later reads four bytes from inside that freed region. Exploitation requires Yasm to process the crafted input; the project expects inputs to be trusted and therefore disputes that the demonstrated process abort has a security consequence.
The record
- CVE
- CVE-2023-31972
- Published
- May 9, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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.
Public exploit references
- 170-UAF proof-of-concept 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