Skip to content
Fencer Intel
high 7.1

CVE-2020-24119 json

A heap buffer overflow read was discovered in upx 4.0.0, because the check in p_lx_elf.cpp is not perfect.

published 5y ago modified 4mo ago also EUVD-2020-16855

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

A heap buffer overflow read was discovered in upx 4.0.0, because the check in p_lx_elf.cpp is not perfect.

Patch / fix

  • upx-ucl Debian 14, Debian 13 4.2.2-1

debian advisories DEBIAN-CVE-2020-24119

  • upx openSUSE Tumbleweed 3.96-3.2
  • upx Package Hub 15 SP2 3.96-bp152.2.3.1
  • upx Package Hub 15 SP3, openSUSE Leap 15.3, openSUSE Leap 15.2 3.96-bp153.2.3.1

opensuse advisories openSUSE-SU-2024:11486-1openSUSE-SU-2021:0826-1openSUSE-SU-2021:0813-1

  • upx Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 4.0.0-r0

alpine advisories ALPINE-CVE-2020-24119

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-24119 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-24119 updated cvss 6.3

upx: heap buffer overflow in p_lx_elf.cpp

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/upx/upx/issues/388 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.