LiveActive security incident?Get immediate response
CVE Record

CVE-2020-27797: An invalid memory address reference was discovered in the elf_lookup function in p_lx_elf.cpp in UPX 4.0.0...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a memory-safety flaw in UPX 4.0.0 development build handling a crafted Mach-O file. Business urgency depends on whether UPX processes untrusted files in build, analysis, or security tooling workflows. The sources do not provide a CVSS score, confirmed impact beyond invalid memory access, or a named fixed version.

Executive priority

Treat this as a targeted toolchain and analysis-workflow risk, not a broad enterprise emergency from current evidence. Prioritize teams that process untrusted binaries, especially macOS Mach-O files, and require confirmation of UPX versions and isolation controls.

Technical view

The reported issue is an invalid memory address reference in UPX's elf_lookup function in p_lx_elf.cpp, triggered via a crafted Mach-O file. The CVE maps to CWE-119 and lists upx 4.0.0-git-87b73e5cfdc1+ as affected. Evidence is limited to the CVE record and linked GitHub issue.

Likely exposure

Exposure is most likely where the affected UPX build parses Mach-O files from external users, malware samples, CI inputs, or partner submissions. Systems that do not run UPX, or only process trusted files, have lower apparent exposure based on available sources.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public weaponization, or exploitation in the wild. The known trigger is a crafted Mach-O file processed by the affected UPX build, but the sources do not establish reliable code execution or broader impact.

Researcher notes

The record is sparse: no CVSS vector, no patch reference, and no confirmed exploitation. Assessment should focus on reproducing exposure safely in controlled validation environments, determining whether the affected development build was deployed, and monitoring upstream UPX issue 390 for authoritative remediation detail.

Mitigation direction

  • Inventory UPX usage and remove the affected git build where present.
  • Avoid processing untrusted Mach-O files with the affected UPX build.
  • Run file-processing workflows inside sandboxed, least-privilege environments.
  • Check UPX project guidance and issue 390 for fix status.
  • Use a vendor-recommended fixed build if one is identified.

Validation and detection

  • Confirm whether UPX 4.0.0-git-87b73e5cfdc1+ exists in the environment.
  • Identify pipelines that pass Mach-O files into UPX.
  • Review recent UPX crashes involving Mach-O parsing.
  • Verify sandboxing around UPX-based analysis or build workflows.
  • Track the linked UPX issue for remediation evidence.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-27797 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aupxupx 4.0.0-git-87b73e5cfdc1+Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.