Dmitry Sklyarov

The issue is a Heap-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform a denial-of-service attack.

The issue is a Stack-based Buffer Overflow, allowing unauthenticated remote attackers to execute arbitrary code on the device.

The issue is a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device.

The issue is a Stack-based Buffer Overflow, allowing unauthenticated remote attackers to execute arbitrary code on the device. This can be exploited by remote attackers without authentication.

The issue concerns a Heap-based Buffer Overflow vulnerability in the CL5708IM, allowing unauthenticated remote attackers to exploit this vulnerability and perform a denial-of-service attack.

The issue is related to the storage of sensitive information in cleartext, allowing a remote unauthenticated attacker to disclose this information. As a result, attackers can gain unauthorized access to the MELSEC CPU module and the MELSEC OPC UA server module.

The issue is related to the use of hard-coded passwords in the software, allowing an unauthenticated attacker to disclose sensitive information. This can result in unauthenticated users being able to view programs and project files or execute programs illegally. The vulnerability can be exploited by a remote attacker to gain access to protected information.

The issue allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated attackers may view programs and project files or execute programs illegally.

The issue allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated attackers may view programs and project files or execute programs illegally.

The issue allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated users may view programs and project files or execute programs illegally.

The issue allows a remote unauthenticated attacker to disclose sensitive information due to the use of a hard-coded cryptographic key. This enables unauthenticated users to view programs and project files or execute programs illegally.

The issue is related to insufficient access control in the Intel(R) Trace Hub driver, which may allow an attacker to escalate privileges. For some Intel(R) Trace Hub instances, it is possible to activate test or debug logic at runtime, potentially enabling an unauthenticated user with physical access to escalate privileges.

The issue is related to the cleartext storage of sensitive information in the programable logic controllers of the affected devices. This allows a remote unauthenticated attacker to disclose a file in a legitimate user's product by using previously eavesdropped cleartext information and to counterfeit a legitimate user’s system.

The issue is related to the use of a weak hash in the password storage mechanism, allowing a remote unauthenticated attacker to login to the product by using a password reversed from a previously eavesdropped password hash. This could potentially lead to unauthorized access to protected information.

The issue is related to the use of a password hash instead of the password for authentication, allowing a remote unauthenticated attacker to login to the product by replaying an eavesdropped password hash. This may enable an attacker to gain unauthorized access to protected information.

The issue is related to the activation of test or debug logic at runtime for some Intel(R) processors, which may allow an unauthenticated user to potentially enable escalation of privilege via physical access. This is due to insufficient protection of service data in the BIOS/UEFI firmware. Exploitation of the issue may allow an attacker to gain elevated privileges and access sensitive information. The problem is also associated with a debugging functionality that has excessive privileges, potentially allowing attackers to read encrypted files.

Name of the Vulnerable Software and Affected Versions: Verifone MX900 series Pinpad Payment Terminals version 30251000 Description: The issue allows for the installation of unsigned packages on the Verifone MX900 series Pinpad Payment Terminals. Recommendations: For version 30251000, ensure that only signed packages are installed to prevent potential exploitation. As a temporary workaround, consider restricting package installation privileges until a patch is available.

Name of the Vulnerable Software and Affected Versions: Verifone Verix OS on VerixV Pinpad Payment Terminals with QT000530 Description: A buffer overflow issue exists via the Run system call. Recommendations: For Verifone Verix OS on VerixV Pinpad Payment Terminals with QT000530, at the moment, there is no information about a newer version that contains a fix for this issue.

Name of the Vulnerable Software and Affected Versions: Verifone MX900 series Pinpad Payment Terminals version 30251000 Description: The issue concerns Insecure Permissions, which can lead to arbitrary command injection and privilege escalation through svc netcontrol. Recommendations: For Verifone MX900 series Pinpad Payment Terminals version 30251000, consider restricting access to the svc netcontrol service to minimize the risk of exploitation until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Verifone VerixV Pinpad Payment Terminals version QT000530 Description: The issue allows bypass of integrity and origin control for S1G file generation. Recommendations: For Verifone VerixV Pinpad Payment Terminals version QT000530, at the moment, there is no information about a newer version that contains a fix for this vulnerability.