Brocade Sannav

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.

Published: 2025-02-14T03:47:35.931Z
Updated: 2025-09-09T19:03:10.704Z

Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.

Published: 2025-02-14T23:33:06.196Z
Updated: 2025-02-18T16:27:47.563Z

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.

Published: 2024-04-25T07:30:44.685Z
Updated: 2024-08-01T20:33:52.534Z

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.

Published: 2024-04-25T02:32:08.686Z
Updated: 2024-08-01T20:33:52.517Z

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.

Published: 2024-04-25T01:58:17.489Z
Updated: 2024-08-01T20:33:52.913Z

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.

Published: 2024-05-08T01:01:54.775Z
Updated: 2024-08-01T19:25:42.147Z

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.

Published: 2024-04-27T00:06:10.084Z
Updated: 2025-03-19T18:23:52.688Z

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.

Published: 2025-02-14T04:53:11.643Z
Updated: 2025-02-14T15:28:53.249Z

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.

Published: 2024-04-19T05:24:44.930Z
Updated: 2024-08-02T01:17:58.693Z

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.

Published: 2024-04-19T05:17:57.502Z
Updated: 2024-09-18T22:32:12.764Z

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.

Published: 2024-04-19T05:06:45.286Z
Updated: 2024-08-02T01:17:58.699Z

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.

Published: 2024-04-19T04:53:59.021Z
Updated: 2024-08-02T01:17:58.656Z

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.

Published: 2024-04-19T04:48:46.279Z
Updated: 2024-08-02T01:17:58.599Z

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.

Published: 2024-04-19T04:39:17.273Z
Updated: 2024-09-18T22:30:38.120Z

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.

Published: 2024-04-19T04:04:48.344Z
Updated: 2024-08-02T01:17:58.554Z

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.

Published: 2024-04-19T04:15:43.213Z
Updated: 2024-08-02T01:17:58.555Z

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 Brocade SANnav appliance.

Published: 2024-04-19T03:59:25.379Z
Updated: 2024-08-02T01:17:58.481Z

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.

Published: 2024-04-19T03:30:51.466Z
Updated: 2024-08-02T01:17:58.593Z

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.

Published: 2024-04-19T03:19:28.271Z
Updated: 2024-08-02T01:17:58.492Z

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.

Published: 2024-04-19T03:15:32.394Z
Updated: 2024-08-02T01:17:58.622Z

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.

Published: 2024-04-19T03:11:25.892Z
Updated: 2024-08-02T01:17:58.659Z

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.

Published: 2024-04-18T01:00:49.444Z
Updated: 2024-08-02T01:17:58.555Z

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.

Published: 2024-04-17T22:11:51.261Z
Updated: 2024-08-02T01:17:58.612Z

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.

Published: 2024-04-17T21:43:57.482Z
Updated: 2024-08-02T01:17:58.546Z

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.

Published: 2024-04-17T19:21:32.090Z
Updated: 2024-08-02T01:17:58.619Z

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.

Published: 2024-04-17T18:21:35.720Z
Updated: 2024-08-02T01:17:58.630Z

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.

Published: 2025-02-14T23:23:18.826Z
Updated: 2025-02-18T16:28:38.800Z

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 exists because of an incomplete fix for CVE-2024-29952

Published: 2025-02-14T03:13:19.662Z
Updated: 2025-02-14T15:46:28.704Z

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.

Published: 2023-08-31T00:20:30.874Z
Updated: 2024-09-27T19:12:13.928Z

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.

Published: 2022-12-09T01:48:24.949Z
Updated: 2025-04-22T20:26:49.948Z