Bug 1948692 (CVE-2021-30500) - CVE-2021-30500 upx: Null pointer dereference in PackLinuxElf::canUnpack() in p_lx_elf.cpp
Summary: CVE-2021-30500 upx: Null pointer dereference in PackLinuxElf::canUnpack() in ...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-30500
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1948693 1948694
Blocks: 1948699
TreeView+ depends on / blocked
 
Reported: 2021-04-12 18:37 UTC by Pedro Sampaio
Modified: 2021-04-13 13:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-13 00:38:56 UTC
Embargoed:

Attachments (Terms of Use)

Description Pedro Sampaio 2021-04-12 18:37:55 UTC 
Null pointer dereference was found in upx PackLinuxElf::canUnpack() in p_lx_elf.cpp,in version UPX 4.0.0. That allow attackers to execute
arbitrary code and cause a denial of service via a crafted file.

Upstream issue:

https://github.com/upx/upx/issues/48

Upstream patch:

https://github.com/upx/upx/commit/90279abdfcd235172eab99651043051188938dcc
Comment 1 Pedro Sampaio 2021-04-12 18:38:22 UTC 
Created upx tracking bugs for this issue:

Affects: epel-all [bug 1948693]
Affects: fedora-all [bug 1948694]
Comment 2 Product Security DevOps Team 2021-04-13 00:38:56 UTC 
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.
Comment 3 Salvatore Bonaccorso 2021-04-13 07:02:09 UTC 
(In reply to Pedro Sampaio from comment #0)
> Null pointer dereference was found in upx PackLinuxElf::canUnpack() in
> p_lx_elf.cpp,in version UPX 4.0.0. That allow attackers to execute
> arbitrary code and cause a denial of service via a crafted file.
> 
> Upstream issue:
> 
> https://github.com/upx/upx/issues/48
> 
> Upstream patch:
> 
> https://github.com/upx/upx/commit/90279abdfcd235172eab99651043051188938dcc



Should the upstream issue to b referenced be https://github.com/upx/upx/issues/485 (missing last 5 digit in the issue number instead of 48)?
Comment 4 Gwyn Ciesla 2021-04-13 13:13:17 UTC 
Yes, that's correct.
Note You need to log in before you can comment on or make changes to this bug.