Code execution via aprintf stack-buffer overflow
Published Jul 18, 2023 · Updated Oct 28, 2024
Stack-based buffer overflow in ATasm 1.09 allows attackers to execute arbitrary code via a crafted assembly source file. The aprintf() function in asm.c writes attacker-controlled formatted output beyond a stack buffer while processing the file. ATasm must process the crafted file to trigger the overflow, and successful exploitation runs code with the privileges of the ATasm process.
Summary
What happened
Stack-based buffer overflow in ATasm 1.09 allows attackers to execute arbitrary code via a crafted assembly source file. The aprintf() function in asm.c writes attacker-controlled formatted output beyond a stack buffer while processing the file. ATasm must process the crafted file to trigger the overflow, and successful exploitation runs code with the privileges of the ATasm process.
The record
- CVE
- CVE-2021-34123
- Published
- Jul 18, 2023
- Updated
- Oct 28, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 18, 2023CVE publishedPublication date reported by the CVE source.
- Oct 28, 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
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