Search
Search Results (13 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-82370 | 1 Brocade | 1 Sannav | 2026-09-24 | N/A |
| Unauthenticated remote command injection in the Brocade SANnav orchestrator HTTP service permits network-adjacent attackers to execute arbitrary administrative switch CLI commands and issue container management instructions. This could allow an attacker to alter Fibre Channel fabric switch configurations or manipulate application container runtimes. This vulnerability affects Brocade SANnav versions before 3.0.1a. | ||||
| CVE-2026-82368 | 1 Brocade | 1 Sannav | 2026-09-23 | N/A |
| Insecure access controls on internal service ports in Brocade SANnav versions before 3.0.1a allow local, non-administrative host users to communicate directly with backend management services. A local attacker can leverage this exposed access to transmit commands to connected Fabric OS switches under the security context of the SANnav management user. | ||||
| CVE-2026-82369 | 1 Brocade | 1 Sannav | 2026-09-23 | N/A |
| Insufficient input sanitization of shell metacharacters in the Brocade SANnav CLI scripting component permits authenticated users to break out of restricted execution contexts on managed switches. An attacker with command execution permissions can leverage this flaw to run unauthorized shell commands across target fabric switches, bypassing command allow-lists and obtaining full administrative switch access. This vulnerability affects all Brocade SANnav versions before 3.0.1a. | ||||
| CVE-2025-12679 | 2 Broadcom, Brocade | 2 Sannav, Sannav | 2026-03-03 | 6.5 Medium |
| A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. Note: The vulnerability is only triggered during a migration and not in a new installation. The system audit logs are accessible only to a privileged user on the server. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user. | ||||
| CVE-2025-12680 | 2 Broadcom, Brocade | 2 Sannav, Sannav | 2026-03-03 | 4.9 Medium |
| Brocade SANnav before Brocade SANnav 2.4.0b logs database passwords in clear text in the standby SANnav server, after disaster recovery failover. The vulnerability could allow a remote authenticated attacker with admin privilege able to access the SANnav logs or the supportsave to read the database password. | ||||
| CVE-2025-12773 | 2 Broadcom, Brocade | 2 Sannav, Sannav | 2026-03-03 | 6.5 Medium |
| A vulnerability in update-reports-purge-settings.sh script logging for Brocade SANnav before 2.4.0a could allow the collection of SANnav database password in the system audit logs. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the Brocade SANnav database password. | ||||
| CVE-2025-12774 | 2 Broadcom, Brocade | 2 Sannav, Sannav | 2026-03-03 | 7.5 High |
| A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. An attacker with access to Brocade SANnav supportsave file, could open the file and then obtain sensitive information such as details of database tables and encrypted passwords. | ||||
| CVE-2025-12772 | 2 Broadcom, Brocade | 2 Sannav, Sannav | 2026-02-09 | 4.9 Medium |
| Brocade SANnav before 2.4.0b logs the Brocade Fabric OS Switch admin password on the SANnav support save logs. When OOM occurs on a Brocade SANnav server, the call stack trace for the Brocade switch is also collected in the heap dump file which contains this switch password in clear text. The vulnerability could allow a remote authenticated attacker with admin privilege able to access the SANnav logs or the supportsave to read the switch admin password. | ||||
| CVE-2024-2240 | 2 Broadcom, Brocade | 2 Brocade Sannav, Sannav | 2025-08-26 | 7.2 High |
| 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 | 2 Broadcom, Brocade | 2 Brocade Sannav, Sannav | 2025-08-26 | 5.3 Medium |
| 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-4282 | 2 Broadcom, Brocade | 2 Brocade Sannav, Sannav | 2025-08-26 | 9.8 Critical |
| Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. | ||||
| 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.