CVE-2019-20053
published 2019-12-27CVE-2019-20053: An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.
PriorityP418medium5.5CVSS 3.1
AVLACLPRNUIRSUCNINAH
EPSS
1.23%
65.1th percentile
An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | upx-ucl | < upx-ucl 3.96-1 (bullseye) | upx-ucl 3.96-1 (bullseye) |
| opensuse | backports | — | — |
| opensuse | leap | — | — |
| upx | upx | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:N/A:P
osv5.5MEDIUM
vendor_debian5.5LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-phmx-286h-jcc3: An invalid memory address dereference was discovered in the canUnpack function in p_mach
ghsa_unreviewed·2022-05-24
CVE-2019-20053 [MEDIUM] CWE-119 GHSA-phmx-286h-jcc3: An invalid memory address dereference was discovered in the canUnpack function in p_mach
An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.
OSV
CVE-2019-20053: An invalid memory address dereference was discovered in the canUnpack function in p_mach
osv·2019-12-27·CVSS 5.5
CVE-2019-20053 [MEDIUM] CVE-2019-20053: An invalid memory address dereference was discovered in the canUnpack function in p_mach
An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.
Debian
CVE-2019-20053: upx-ucl - An invalid memory address dereference was discovered in the canUnpack function i...
vendor_debian·2019·CVSS 5.5
CVE-2019-20053 [MEDIUM] CVE-2019-20053: upx-ucl - An invalid memory address dereference was discovered in the canUnpack function i...
An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.
Scope: local
bullseye: resolved (fixed in 3.96-1)
forky: resolved (fixed in 3.96-1)
sid: resolved (fixed in 3.96-1)
trixie: resolved (fixed in 3.96-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp
bugzilla·2020-01-23·CVSS 5.5
CVE-2019-20053 [MEDIUM] CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp
An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.
Reference:
https://github.com/upx/upx/issues/314
Discussion:
Created upx tracking bugs for this issue:
Affects: epel-7 [bug 1794534]
Affects: epel-8 [bug 1794535]
Affects: fedora-all [bug 1794533]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Bugzilla
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [epel-7]
bugzilla·2020-01-23·CVSS 5.5
CVE-2019-20053 [MEDIUM] CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [epel-7]
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to
Bugzilla
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [epel-8]
bugzilla·2020-01-23·CVSS 5.5
CVE-2019-20053 [MEDIUM] CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [epel-8]
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [epel-8]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-8.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to
Bugzilla
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [fedora-all]
bugzilla·2020-01-23·CVSS 5.5
CVE-2019-20053 [MEDIUM] CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [fedora-all]
CVE-2019-20053 upx: invalid memory address dereference in canUnpack in p_mach.cpp [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple s
http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00003.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-02/msg00007.htmlhttps://github.com/upx/upx/issues/314http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00003.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-02/msg00007.htmlhttps://github.com/upx/upx/issues/314
2019-12-27
Published