Filtered by vendor Brocade
Subscriptions
Filtered by product Sannav
Subscriptions
Total
5 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2024-4282 | 1 Brocade | 1 Sannav | 2025-07-13 | N/A |
| Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. | ||||
| CVE-2024-2240 | 1 Brocade | 1 Sannav | 2025-07-13 | N/A |
| Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could allow a remote authenticated attacker to execute various attacks. | ||||
| CVE-2024-10405 | 1 Brocade | 1 Sannav | 2025-07-12 | N/A |
| Brocade SANnav before SANnav 2.3.1b enables weak TLS ciphers on ports 443 and 18082. In case of a successful exploit, an attacker can read Brocade SANnav data stream that includes monitored Brocade Fabric OS switches performance data, port status, zoning information, WWNs, IP Addresses, but no customer data, no personal data and no secrets or passwords, as it travels across the network. | ||||
| CVE-2024-29964 | 2 Broadcom, Brocade | 2 Brocade Sannav, Sannav | 2025-02-04 | 5.7 Medium |
| Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files. An unprivileged attacker who gains access to the server can read sensitive information from these files. | ||||
| CVE-2022-28161 | 1 Brocade | 1 Sannav | 2024-11-21 | 5.5 Medium |
| An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh passwords in filetansfer.log in debug mode. To exploit this vulnerability, the attacker would need to have valid user credentials and turn on debug mode. | ||||
Page 1 of 1.