Broadcom Brocade Sannav vulnerabilities

CVE-2024-29969 [HIGH] CWE-326 CVE-2024-29969: When a Brocade SANnav installation is upgraded from Brocade SANnav v2.2.2 to Brocade SANnav 2.3.0, T 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.

CVE-2024-29957 [HIGH] CWE-532 CVE-2024-29957: When Brocade SANnav before v2.3.1 and v2.3.0a servers are configured in Disaster Recovery mode, the When Brocade SANnav before v2.3.1 and v2.3.0a servers are configured in Disaster Recovery mode, the encryption key is stored in the DR log files. This could provide attackers with an additional, less-protected path to acquiring the encryption key.

CVE-2024-29961 [HIGH] CWE-200 CVE-2024-29961: A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service to send ping commands in the background at regular intervals to gridgain.com to check if updates are available for the Component. This could make an unauthenticated, remote attacker aware of the behavior and launch a supply-chain attack against a Broca

CVE-2024-29959 [HIGH] CWE-532 CVE-2024-29959: A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypte A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save.

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.

CVE-2024-29968 [HIGH] 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-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-2024-29958 [HIGH] 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-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-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-2024-29963 [LOW] CWE-798 CVE-2024-29963: Brocade SANnav OVA before v2.3.1, and v2.3.0a, contain hardcoded TLS keys used by Docker. Note: Bro Brocade SANnav OVA before v2.3.1, and v2.3.0a, contain hardcoded TLS keys used by Docker. Note: Brocade SANnav doesn't have access to remote Docker registries.

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-29955 [MEDIUM] CWE-532 CVE-2024-29955: A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print t A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs. This could provide attackers with an additional, less-protected path to acquiring the encryption key.

CVE-2024-29952 [MEDIUM] CWE-312 CVE-2024-29952: A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to pri A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to print the Auth, Priv, and SSL key store passwords in unencrypted logs by manipulating command variables.

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-2024-29950 [HIGH] 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-2023-31424 [HIGH] CWE-290 CVE-2023-31424: Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a allows remote unauthenticated Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a allows remote unauthenticated users to bypass web authentication and authorization.

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-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-2022-33187 [MEDIUM] CWE-532 CVE-2022-33187: Brocade SANnav before v2.2.1 logs usernames and encoded passwords in debug-enabled logs. The vulner Brocade SANnav before v2.2.1 logs usernames and encoded passwords in debug-enabled logs. The vulnerability could allow an attacker with admin privilege to read sensitive information.