🛡️ CVE-2020-27801 on Debian — upx-ucl
Description
A heap-based buffer over-read was discovered in the get_le64 function in bele.h in UPX 4.0.0 via a crafted Mach-O file.
Distribution advisory
This page covers CVE-2020-27801 as tracked by Debian, for the package upx-ucl. The fix is available in version 4.2.2-1; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
Affected software
DEBIAN-CVE-2020-27801 is recorded against 1 package.
- upx-ucl (fixed in 4.2.2-1)
Timeline and source
Published on 25 August 2022 and last revised on 15 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2020-27801 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| upx-ucl | — | 4.2.2-1 |
References
Similar Threats
- Unknown DEBIAN-CVE-2021-46179
- Unknown DEBIAN-CVE-2021-43311
- Unknown DEBIAN-CVE-2021-43312
- Unknown DEBIAN-CVE-2021-43313
- Unknown DEBIAN-CVE-2021-43314
Free Vulnerability Check
Is your site affected by DEBIAN-CVE-2020-27801?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against DEBIAN-CVE-2020-27801 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.