Code execution via unchecked filename formatting
Published Feb 22, 2021 · Updated Jul 9, 2026
Buffer overflow in Yz1 0.30 and 0.32 allows attackers to execute arbitrary code through a crafted archive file. During archive decoding, unchecked sprintf calls format attacker-controlled filenames into fixed-size stack buffers, overwriting stack state. Exploitation requires a victim to open or extract the crafted archive in an affected archiver; successful exploitation can execute code with that process's privileges.
Summary
What happened
Buffer overflow in Yz1 0.30 and 0.32 allows attackers to execute arbitrary code through a crafted archive file. During archive decoding, unchecked sprintf calls format attacker-controlled filenames into fixed-size stack buffers, overwriting stack state. Exploitation requires a victim to open or extract the crafted archive in an affected archiver; successful exploitation can execute code with that process's privileges.
The record
- CVE
- CVE-2020-24175
- Published
- Feb 22, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2021CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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
- yz1 exploit.py 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