CVE-2020-27797 Null dereference in upx
Medium 5.5
Published
Updated
Check this codebase for CVE-2020-27797 and fix it if it is affected.
What it is: CVE-2020-27797 is a medium-severity vulnerability in upx, published on 25 Aug 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-27797 in the wild and no public exploit code.
Affected product: upx. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2020-27797/ (Markdown: https://insights.sbomify.com/CVE-2020-27797/index.md)
A crafted Mach-O file causes a null pointer dereference in UPX, leading to a denial of service during processing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2020-27797?
CVE-2020-27797 is a medium-severity vulnerability in upx, published on 25 Aug 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
An invalid memory address reference was discovered in the elf_lookup function in p_lx_elf.cpp in UPX 4.0.0 via a crafted Mach-O file.
Which versions are affected by CVE-2020-27797?
It affects 1 product.
Products include Upx Upx.
How do I fix CVE-2020-27797?
Upgrade to a fixed version.
Is CVE-2020-27797 being exploited?
There is no known exploitation of CVE-2020-27797 in the wild and no public exploit code.
Other vulnerabilities in upx
Sources
Also known as DEBIAN-CVE-2020-27797, GHSA-x97v-6wf2-6ffp, UBUNTU-CVE-2020-27797.