Brocade Sannav vulnerabilities

CVE-2024-4282 [HIGH] CWE-327 CVE-2024-4282: Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.

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 passwo

CVE-2024-2240 [HIGH] CWE-250 CVE-2024-2240: Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could 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-2025-1053 [HIGH] 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-2024-10404 [MEDIUM] CWE-312 CVE-2024-10404: CalInvocationHandler in Brocade SANnav before 2.3.1b logs sensitive information in clear text. The 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 con

CVE-2024-2860 [HIGH] CWE-306 CVE-2024-2860: The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect 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.

CVE-2024-2859 [HIGH] CWE-276 CVE-2024-2859: By default, SANnav OVA is shipped with root user login enabled. While protected by a password, acce 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.

CVE-2024-4173 [CRITICAL] CWE-200 CVE-2024-4173: A vulnerability in Brocade SANnav exposes Kafka in the wan interface. The vulnerability could allo 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.

CVE-2024-4161 [HIGH] CWE-319 CVE-2024-4161: In Brocade SANnav, before Brocade SANnav v2.3.0, syslog traffic received clear text. This could all 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.

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-29966 [CRITICAL] CWE-798 CVE-2024-29966: Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation tha Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance's root password. The vulnerability could allow an unauthenticated attacker full access to the Brocade SANnav appliance.

CVE-2024-29960 [HIGH] CWE-798 CVE-2024-29960: In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical in the VM every time SANnav is installed. Any Brocade SAnnav VM based on the official OVA images is vulnerable to MITM over SSH. An attacker can decrypt and compromise the SSH traffic to the SANnav.

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-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-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-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 [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-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-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.