| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in UPX and classified as critical. This vulnerability affects the function invert_pt_dynamic of the file p_lx_elf.cpp. Executing a manipulation can lead to memory corruption.
This vulnerability is registered as CVE-2020-27787. It is possible to launch the attack remotely. No exploit is available.
A patch should be applied to remediate this issue.
Details
A vulnerability has been found in UPX (the affected version is unknown) and classified as critical. This vulnerability affects the function invert_pt_dynamic of the file p_lx_elf.cpp. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. CVE summarizes:
A Segmentaation fault was found in UPX in invert_pt_dynamic() function in p_lx_elf.cpp. An attacker with a crafted input file allows invalid memory address access that could lead to a denial of service.
The weakness was published 08/19/2022 as 333. The advisory is available at github.com. This vulnerability was named CVE-2020-27787 since 10/27/2020. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
Applying the patch e2f60adc95334f47e286838dac33160819c5d74d is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
License
Website
- Product: https://github.com/upx/upx/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: e2f60adc95334f47e286838dac33160819c5d74d
Timeline
10/27/2020 🔍08/19/2022 🔍
08/19/2022 🔍
04/11/2025 🔍
Sources
Product: github.comAdvisory: 333
Status: Confirmed
CVE: CVE-2020-27787 (🔍)
GCVE (CVE): GCVE-0-2020-27787
GCVE (VulDB): GCVE-100-206770
Entry
Created: 08/19/2022 10:56Updated: 04/11/2025 15:35
Changes: 08/19/2022 10:56 (41), 09/18/2022 11:49 (11), 04/11/2025 15:35 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.