Page 14 of 147 results (0.004 seconds)

CVSS: 9.8EPSS: 76%CPEs: 1EXPL: 1

An issue was discovered in Veritas Backup Exec before 21.2. It supports multiple authentication schemes: SHA authentication is one of these. This authentication scheme is no longer used in current versions of the product, but hadn't yet been disabled. An attacker could remotely exploit this scheme to gain unauthorized access to an Agent and execute privileged commands. Se detectó un problema en Veritas Backup Exec versiones anteriores a 21.2. • http://packetstormsecurity.com/files/168506/Veritas-Backup-Exec-Agent-Remote-Code-Execution.html https://www.veritas.com/content/support/en_US/security/VTS21-001#issue1 https://www.veritas.com/content/support/en_US/security/VTS21-001 • CWE-287: Improper Authentication •

CVSS: 9.0EPSS: 70%CPEs: 1EXPL: 1

An issue was discovered in Veritas Backup Exec before 21.2. The communication between a client and an Agent requires successful authentication, which is typically completed over a secure TLS communication. However, due to a vulnerability in the SHA Authentication scheme, an attacker is able to gain unauthorized access and complete the authentication process. Subsequently, the client can execute data management protocol commands on the authenticated connection. The attacker could use one of these commands to execute an arbitrary command on the system using system privileges. • http://packetstormsecurity.com/files/168506/Veritas-Backup-Exec-Agent-Remote-Code-Execution.html https://www.veritas.com/content/support/en_US/security/VTS21-001#issue3 https://www.veritas.com/content/support/en_US/security/VTS21-001 • CWE-287: Improper Authentication •

CVSS: 8.1EPSS: 74%CPEs: 1EXPL: 1

An issue was discovered in Veritas Backup Exec before 21.2. The communication between a client and an Agent requires successful authentication, which is typically completed over a secure TLS communication. However, due to a vulnerability in the SHA Authentication scheme, an attacker is able to gain unauthorized access and complete the authentication process. Subsequently, the client can execute data management protocol commands on the authenticated connection. By using crafted input parameters in one of these commands, an attacker can access an arbitrary file on the system using System privileges. • http://packetstormsecurity.com/files/168506/Veritas-Backup-Exec-Agent-Remote-Code-Execution.html https://www.veritas.com/content/support/en_US/security/VTS21-001#issue2 https://www.veritas.com/content/support/en_US/security/VTS21-001 • CWE-287: Improper Authentication •

CVSS: 9.3EPSS: 0%CPEs: 2EXPL: 0

An issue was discovered in Veritas System Recovery before 21.2. On start-up, it loads the OpenSSL library from \usr\local\ssl. This library attempts to load the from \usr\local\ssl\openssl.cnf configuration file, which does not exist. By default, on Windows systems, users can create directories under C:\. A low privileged user can create a C:\usr\local\ssl\openssl.cnf configuration file to load a malicious OpenSSL engine, resulting in arbitrary code execution as SYSTEM when the service starts. • https://www.veritas.com/content/support/en_US/security/VTS20-017 •

CVSS: 8.8EPSS: 0%CPEs: 12EXPL: 0

An issue was discovered in Veritas APTARE 10.4 before 10.4P9 and 10.5 before 10.5P3. By default, on Windows systems, users can create directories under C:\. A low privileged user can create a directory at the configuration file locations. When the Windows system restarts, a malicious OpenSSL engine could exploit arbitrary code execution as SYSTEM. This gives the attacker administrator access on the system, allowing the attacker (by default) to access all data, access all installed applications, etc. • https://www.veritas.com/content/support/en_US/security/VTS20-009 •