4 results (0.005 seconds)

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

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 https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/veritas/beagent_sha_auth_rce.rb • CWE-287: Improper Authentication •

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

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 https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/veritas/beagent_sha_auth_rce.rb • CWE-287: Improper Authentication •

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

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 https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/veritas/beagent_sha_auth_rce.rb • CWE-287: Improper Authentication •

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

An issue was discovered in the server in Veritas Backup Exec through 16.2, 20.6 before hotfix 298543, and 21.1 before hotfix 657517. On start-up, it loads the OpenSSL library from the Installation folder. This library in turn attempts to load the /usr/local/ssl/openssl.cnf configuration file, which may not exist. On Windows systems, this path could translate to <drive>:\usr\local\ssl\openssl.cnf. A low privileged user can create a :\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.kb.cert.org/vuls/id/429301 https://www.veritas.com/content/support/en_US/security/VTS20-010 • CWE-434: Unrestricted Upload of File with Dangerous Type •