Search
Search Results (407437 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2021-30500 | 3 Fedoraproject, Redhat, Upx | 3 Fedora, Enterprise Linux, Upx | 2025-04-11 | 7.8 High |
| 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. | ||||
| CVE-2020-27788 | 1 Upx | 1 Upx | 2025-04-11 | 5.5 Medium |
| An out-of-bounds read access vulnerability was discovered in UPX in PackLinuxElf64::canPack() function of p_lx_elf.cpp file. An attacker with a crafted input file could trigger this issue that could cause a crash leading to a denial of service. | ||||
| CVE-2020-27787 | 1 Upx | 1 Upx | 2025-04-11 | 5.5 Medium |
| 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. | ||||
| CVE-2020-27802 | 1 Upx | 1 Upx | 2025-04-11 | 5.5 Medium |
| An floating point exception was discovered in the elf_lookup function in p_lx_elf.cpp in UPX 4.0.0 via a crafted Mach-O file. | ||||
| CVE-2020-27799 | 1 Upx | 1 Upx | 2025-04-11 | 7.8 High |
| A heap-based buffer over-read was discovered in the acc_ua_get_be32 function in miniacc.h in UPX 4.0.0 via a crafted Mach-O file. | ||||
| CVE-2020-27796 | 1 Upx | 1 Upx | 2025-04-11 | 7.8 High |
| A heap-based buffer over-read was discovered in the invert_pt_dynamic function in p_lx_elf.cpp in UPX 4.0.0 via a crafted Mach-O file. | ||||
| CVE-2020-24119 | 2 Fedoraproject, Upx | 2 Fedora, Upx | 2025-04-11 | 7.1 High |
| A heap buffer overflow read was discovered in upx 4.0.0, because the check in p_lx_elf.cpp is not perfect. | ||||
| CVE-2018-11243 | 1 Upx | 1 Upx | 2025-04-11 | N/A |
| PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service (double free), limit the ability of a malware scanner to operate on the entire original data, or possibly have unspecified other impact via a crafted file. | ||||
| CVE-2025-32775 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32774 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32773 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32772 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32771 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32770 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32769 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32768 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32767 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32765 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32764 | 2025-04-11 | N/A | ||
| Not used | ||||
| CVE-2025-32763 | 2025-04-11 | N/A | ||
| Not used | ||||