Compressor crash via oversized read length
Published Aug 22, 2023 · Updated Oct 3, 2024
Reachable assertion in UPX before 4.0.0 allows remote attackers to crash the compressor by supplying a crafted executable file. InputFile::readx asserts that a requested read length does not exceed its MemBuffer size; a crafted Mach-O input reaches the check with an oversized length and aborts the process. Processing requires a user to run UPX against the file, and the demonstrated consequence is termination of that UPX process rather than host-wide service loss.
Summary
What happened
Reachable assertion in UPX before 4.0.0 allows remote attackers to crash the compressor by supplying a crafted executable file. InputFile::readx asserts that a requested read length does not exceed its MemBuffer size; a crafted Mach-O input reaches the check with an oversized length and aborts the process. Processing requires a user to run UPX against the file, and the demonstrated consequence is termination of that UPX process rather than host-wide service loss.
The record
- CVE
- CVE-2021-46179
- Published
- Aug 22, 2023
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 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.
Public exploit references
- UPX readx assertion reproducerproof 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