Broadcom Brocade Sannav vulnerabilities

CVE-2024-29964 [MEDIUM] CWE-732 CVE-2024-29964: Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker f 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-2019-16209 [HIGH] CWE-295 CVE-2019-16209: A vulnerability, in The ReportsTrustManager class of Brocade SANnav versions before v2.0, could allo A vulnerability, in The ReportsTrustManager class of Brocade SANnav versions before v2.0, could allow an attacker to perform a man-in-the-middle attack against Secure Sockets Layer(SSL)connections.

CVE-2024-29968 [MEDIUM] CWE-922 CVE-2024-29968: An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Broc An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Brocade SANnav instances are configured in disaster recovery mode. SQL Table names, column names, and SQL queries are collected in DR standby Supportsave. This could allow authenticated users to access the database structure and its contents.

CVE-2023-31925 [MEDIUM] CWE-312 CVE-2023-31925: Brocade SANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords in plaintext. A pr Brocade SANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords in plaintext. A privileged user could retrieve these credentials with knowledge and access to these log files. SNMP credentials could be seen in SANnav SupportSave if the capture is performed after an SNMP configuration failure causes an SNMP communication log dump.

CVE-2020-15379 [HIGH] CWE-20 CVE-2020-15379: Brocade SANnav before v.2.1.0a could allow remote attackers cause a denial-of-service condition due Brocade SANnav before v.2.1.0a could allow remote attackers cause a denial-of-service condition due to a lack of proper validation, of the length of user-supplied data as name for custom field name.

CVE-2020-15387 [HIGH] CWE-326 CVE-2020-15387: The host SSH servers of Brocade Fabric OS before Brocade Fabric OS v7.4.2h, v8.2.1c, v8.2.2, v9.0.0, The host SSH servers of Brocade Fabric OS before Brocade Fabric OS v7.4.2h, v8.2.1c, v8.2.2, v9.0.0, and Brocade SANnav before v2.1.1 utilize keys of less than 2048 bits, which may be vulnerable to man-in-the-middle attacks and/or insecure SSH communications.

CVE-2024-29956 [MEDIUM] CWE-312 CVE-2024-29956: A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the Brocade SANnav password in cl A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the Brocade SANnav password in clear text in supportsave logs when a user schedules a switch Supportsave from Brocade SANnav.

CVE-2024-29958 [MEDIUM] CWE-532 CVE-2024-29958: A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the encryption key in the console A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the encryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node. This could provide attackers an additional, less protected path to acquiring the encryption key.

CVE-2024-29950 [MEDIUM] CWE-326 CVE-2024-29950: The class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signat The class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signature scheme, which has a SHA-1 hash. The vulnerability could allow a remote, unauthenticated attacker to perform a man-in-the-middle attack.

CVE-2024-4159 [MEDIUM] CWE-200 CVE-2024-4159: Brocade SANnav before v2.3.0a lacks protection mechanisms on port 2377/TCP and 7946/TCP, which coul 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.

CVE-2024-29967 [MEDIUM] CWE-276 CVE-2024-29967: In Brocade SANnav before Brocade SANnav v2.31 and v2.3.0a, it was observed that Docker instances ins In Brocade SANnav before Brocade SANnav v2.31 and v2.3.0a, it was observed that Docker instances inside the appliance have insecure mount points, allowing reading and writing access to sensitive files. The vulnerability could allow a sudo privileged user on the host OS to read and write access to these files.

CVE-2024-10405 [MEDIUM] CWE-327 CVE-2024-10405: Brocade SANnav before SANnav 2.3.1b enables weak TLS ciphers on ports 443 and 18082. In case of a s 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 passwor

CVE-2024-29965 [MEDIUM] CWE-922 CVE-2024-29965: In Brocade SANnav before v2.3.1, and v2.3.0a, it is possible to back up the appliance from the web In Brocade SANnav before v2.3.1, and v2.3.0a, it is possible to back up the appliance from the web interface or the command line interface ("SSH"). The resulting backups are world-readable. A local attacker can recover backup files, restore them to a new malicious appliance, and retrieve the passwords of all the switches.

CVE-2022-43936 [MEDIUM] CWE-532 CVE-2022-43936: Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enable Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled.

CVE-2024-29951 [MEDIUM] CWE-326 CVE-2024-29951: Brocade SANnav before v2.3.1 and v2.3.0a uses the SHA-1 hash in internal SSH ports that are not open Brocade SANnav before v2.3.1 and v2.3.0a uses the SHA-1 hash in internal SSH ports that are not open to remote connection.

CVE-2023-31423 [MEDIUM] CWE-312 CVE-2023-31423: Possible information exposure through log file vulnerability where sensitive fields are recorded i Possible information exposure through log file vulnerability where sensitive fields are recorded in the configuration log without masking on Brocade SANnav before v2.3.0 and 2.2.2a. Notes: To access the logs, the local attacker must have access to an already collected Brocade SANnav "supportsave" outputs.

CVE-2025-1053 [MEDIUM] CWE-532 CVE-2025-1053: Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be 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.

CVE-2022-43937 [MEDIUM] CWE-532 CVE-2022-43937: Possible information exposure through log file vulnerability where sensitive fields are recorded in 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

CVE-2019-16206 [MEDIUM] CWE-311 CVE-2019-16206: The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credent The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' logging level; which could allow a local authenticated attacker to access sensitive information.

CVE-2024-29962 [MEDIUM] CWE-276 CVE-2024-29962: Brocade SANnav OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes fil Brocade SANnav OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes files world-readable. This could allow a local user without the required privileges to access sensitive information or a Java binary.