Vulnerabilities > Broadcom > Sannav > High
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-06-27 | CVE-2022-28166 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Broadcom Sannav 2.1.0/2.1.1/2.2.0.0 In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Static Key Ciphers (ssl-static-key-ciphers) on ports 443 & 18082. | 7.5 |
| 2022-06-27 | CVE-2022-28168 | Insecure Storage of Sensitive Information vulnerability in Broadcom Sannav 2.1.0/2.1.1/2.2.0.0 In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored using Base64 encoding, which could allow an attacker able to access log files to easily decode the passwords. | 7.5 |
| 2022-05-06 | CVE-2022-28165 | Unspecified vulnerability in Broadcom Sannav 2.1.0/2.1.1/2.1.1.8 A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an authenticated, remote attacker to access resources that they should not be able to access and perform actions that they should not be able to perform. | 8.8 |
| 2021-06-09 | CVE-2020-15380 | Information Exposure Through Log Files vulnerability in Broadcom Sannav 2.1.0 Brocade SANnav before version 2.1.1 logs account credentials at the ‘trace’ logging level. | 7.5 |
| 2021-06-09 | CVE-2020-15381 | Insufficiently Protected Credentials vulnerability in Broadcom Sannav 2.1.0 Brocade SANnav before version 2.1.1 contains an Improper Authentication vulnerability that allows cleartext transmission of authentication credentials of the jmx server. | 7.5 |