This page lists publicly disclosed CVE vulnerabilities affecting broadcom brocade_sannav (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-6392 | Brocade SANnav before Brocade SANnav 2.4.0a could log database passwords in clear text in audit logs when the daily data dump collector invokes docker exec commands. 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. | [email protected] | 6.7 | 0.10% | 2025-07-10 | 2026-06-17 |
| CVE-2025-6390 | Brocade SANnav before SANnav 2.4.0a logs passwords and pbe keys in the Brocade SANnav server audit logs after installation and under specific conditions. 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. | [email protected] | 5.1 | 0.10% | 2025-07-10 | 2026-06-17 |
| CVE-2025-4662 | Brocade SANnav before SANnav 2.4.0a logs plaintext passphrases in the Brocade SANnav host server audit logs while executing OpenSSL command using a passphrase from the command line or while providing the passphrase through a temporary file. 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. | [email protected] | 5.1 | 0.10% | 2025-07-10 | 2026-06-17 |
| CVE-2024-4282 | Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. | [email protected] | 8.2 | 0.27% | 2025-02-14 | 2026-06-17 |
| CVE-2024-10405 | 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. | [email protected] | 6.9 | 0.18% | 2025-02-14 | 2026-06-17 |
| CVE-2024-2240 | 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. | [email protected] | 8.6 | 0.47% | 2025-02-14 | 2026-06-17 |
| CVE-2025-1053 | Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obtained from a Brocade SANnav supportsave. An attacker with privileged access to the Brocade SANnav database could use the encryption key to obtain passwords used by Brocade SANnav. | [email protected] | 8.6 | 0.14% | 2025-02-13 | 2026-06-17 |
| CVE-2024-10404 | CalInvocationHandler in Brocade SANnav before 2.3.1b logs sensitive information in clear text. The vulnerability could allow an authenticated, local attacker to view Brocade Fabric OS switch sensitive information in clear text. An attacker with administrative privileges could retrieve sensitive information including passwords; SNMP responses that contain AuthSecret and PrivSecret after collecting a “supportsave” or getting access to an already collected “supportsave”. NOTE: this issue exi | [email protected] | 5.5 | 0.10% | 2025-02-13 | 2026-06-17 |
| CVE-2022-43937 | Possible information exposure through log file vulnerability where sensitive fields are recorded in the debug-enabled logs when debugging is turned on in Brocade SANnav before 2.3.0 and 2.2.2a | [email protected] | 5.7 | 0.46% | 2024-11-21 | 2026-06-17 |
| CVE-2022-43936 | Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled. | [email protected] | 6.8 | 0.77% | 2024-11-21 | 2026-06-17 |
| CVE-2022-43935 | An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where Brocade Fabric OS Switch passwords and authorization IDs are printed in the embedded MLS DB file. | [email protected] | 5.3 | 0.22% | 2024-11-21 | 2026-06-17 |
| CVE-2022-43934 | Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095. | [email protected] | 6.5 | 0.47% | 2024-11-21 | 2026-06-17 |
| CVE-2022-43933 | An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where configuration secrets are logged in supportsave. Supportsave file is generated by an admin user troubleshooting the switch. The Logged information may include usernames and passwords, and secret keys. | [email protected] | 4.4 | 0.26% | 2024-11-21 | 2026-06-17 |
| CVE-2024-3596 | RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature. | [email protected] | 9.0 | 14.86% | 2024-07-09 | 2026-06-17 |
| CVE-2024-2860 | The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect local authentication flaw. An attacker accessing the VM where the Brocade SANnav is installed can gain access to sensitive data inside the PostgreSQL database. | [email protected] | 7.8 | 0.16% | 2024-05-07 | 2026-06-17 |
| CVE-2024-2859 | By default, SANnav OVA is shipped with root user login enabled. While protected by a password, access to root could expose SANnav to a remote attacker should they gain access to the root account. | [email protected] | 6.8 | 0.85% | 2024-04-26 | 2026-06-17 |
| CVE-2024-4173 | A vulnerability in Brocade SANnav exposes Kafka in the wan interface. The vulnerability could allow an unauthenticated attacker to perform various attacks, including DOS against the Brocade SANnav. | [email protected] | 7.6 | 0.59% | 2024-04-25 | 2026-06-17 |
| CVE-2024-4161 | In Brocade SANnav, before Brocade SANnav v2.3.0, syslog traffic received clear text. This could allow an unauthenticated, remote attacker to capture sensitive information. | [email protected] | 8.6 | 0.47% | 2024-04-25 | 2026-06-17 |
| CVE-2024-4159 | Brocade SANnav before v2.3.0a lacks protection mechanisms on port 2377/TCP and 7946/TCP, which could allow an unauthenticated attacker to sniff the SANnav Docker information. | [email protected] | 4.3 | 0.52% | 2024-04-25 | 2026-06-17 |
| CVE-2024-29969 | When a Brocade SANnav installation is upgraded from Brocade SANnav v2.2.2 to Brocade SANnav 2.3.0, TLS/SSL weak message authentication code ciphers are added by default for port 18082. | [email protected] | 7.5 | 0.29% | 2024-04-19 | 2026-06-17 |