Show filters
5 Total Results
Displaying 1-5 of 5
Sort by:
Attacker Value
Very High
CVE-2024-3094
Disclosure Date: March 29, 2024 (last updated February 26, 2025)
Malicious code was discovered in the upstream tarballs of xz, starting with version 5.6.0.
Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used by any software linked against this library, intercepting and modifying the data interaction with this library.
5
Attacker Value
Unknown
CVE-2024-4978
Disclosure Date: May 23, 2024 (last updated February 26, 2025)
Justice AV Solutions Viewer Setup 8.3.7.250-1 contains a malicious binary when executed and is signed with an unexpected authenticode signature. A remote, privileged threat actor may exploit this vulnerability to execute of unauthorized PowerShell commands.
0
Attacker Value
Unknown
CVE-2023-2003
Disclosure Date: July 13, 2023 (last updated February 25, 2025)
Embedded malicious code vulnerability in Vision1210, in the build 5 of operating system version 4.3, which could allow a remote attacker to store base64-encoded malicious code in the device's data tables via the PCOM protocol, which can then be retrieved by a client and executed on the device.
0
Attacker Value
Unknown
CVE-2021-22887
Disclosure Date: March 16, 2021 (last updated February 22, 2025)
A vulnerability in the BIOS of Pulse Secure (PSA-Series Hardware) models PSA5000 and PSA7000 could allow an attacker to compromise BIOS firmware. This vulnerability can be exploited only as part of an attack chain. Before an attacker can compromise the BIOS, they must exploit the device.
0
Attacker Value
Unknown
CVE-2020-15165
Disclosure Date: August 28, 2020 (last updated February 22, 2025)
Version 1.1.6-free of Chameleon Mini Live Debugger on Google Play Store may have had it's sources or permissions tampered by a malicious actor. The official maintainer of the package is recommending all users upgrade to v1.1.8 as soon as possible. For more information, review the referenced GitHub Security Advisory.
0