Process crash via out-of-bounds error formatting
Published Jan 12, 2023 · Updated Apr 7, 2025
Improper bounds handling in UPX 4.0.1 allows attackers to crash the packer through a crafted 64-bit Linux ELF file. When an ELF dynamic offset lies beyond EOF, PackLinuxElf64::invert_pt_dynamic reads dt_names[k] out of bounds while formatting the rejection message. A victim must run UPX on the crafted file; the resulting invalid memory access terminates the UPX process.
Summary
What happened
Improper bounds handling in UPX 4.0.1 allows attackers to crash the packer through a crafted 64-bit Linux ELF file. When an ELF dynamic offset lies beyond EOF, PackLinuxElf64::invert_pt_dynamic reads dt_names[k] out of bounds while formatting the rejection message. A victim must run UPX on the crafted file; the resulting invalid memory access terminates the UPX process.
The record
- CVE
- CVE-2023-23457
- Published
- Jan 12, 2023
- Updated
- Apr 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2023CVE publishedPublication date reported by the CVE source.
- Apr 7, 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.
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.
Weakness, pattern, technique
Public exploit references
- POC2 crafted Linux ELF fileproof 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