Process crash via unchecked ELF header
Published May 26, 2021 · Updated Aug 3, 2024
Null pointer dereference in UPX 4.0 allows context-dependent attackers to crash the command-line process via a crafted file. PackLinuxElf::canUnpack processes input as ELF without first validating its header, leading get_le32 to read through a null pointer. A user must invoke UPX decompression on attacker-supplied input; the upstream evidence demonstrates a process abort but not code execution.
Summary
What happened
Null pointer dereference in UPX 4.0 allows context-dependent attackers to crash the command-line process via a crafted file. PackLinuxElf::canUnpack processes input as ELF without first validating its header, leading get_le32 to read through a null pointer. A user must invoke UPX decompression on attacker-supplied input; the upstream evidence demonstrates a process abort but not code execution.
The record
- CVE
- CVE-2021-30500
- Published
- May 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- The UPX Team
- Product
- UPX
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=upx 4.0
What conditions does exploitation require?
What is affected?
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
- Upstream null_pointer_01_get32 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