Sannav

A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. An attacker with access to Brocade SANnav supportsave file, could open the file and then obtain sensitive information such as details of database tables and encrypted passwords.

Published: 2026-02-03T01:28:43.430Z
Updated: 2026-02-03T15:31:59.719Z

A vulnerability in update-reports-purge-settings.sh script logging for Brocade SANnav before 2.4.0a could allow the collection of SANnav database password in the system audit logs. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the Brocade SANnav database password.

Published: 2026-02-03T00:38:08.909Z
Updated: 2026-02-03T20:46:49.012Z

Brocade SANnav before 2.4.0b logs the Brocade Fabric OS Switch admin password on the SANnav support save logs. When OOM occurs on a Brocade SANnav server, the call stack trace for the Brocade switch is also collected in the heap dump file which contains this switch password in clear text. The vulnerability could allow a remote authenticated attacker with admin privilege able to access the SANnav logs or the supportsave to read the switch admin password.

Published: 2026-02-02T22:41:13.921Z
Updated: 2026-02-04T16:53:20.826Z

Brocade SANnav before Brocade SANnav 2.4.0b logs database passwords in clear text in the standby SANnav server, after disaster recovery failover. The vulnerability could allow a remote authenticated attacker with admin privilege able to access the SANnav logs or the supportsave to read the database password.

Published: 2026-02-02T20:50:29.756Z
Updated: 2026-02-03T15:35:13.850Z

A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. Note: The vulnerability is only triggered during a migration and not in a new installation. The system audit logs are accessible only to a privileged user on the server. 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.

Published: 2026-02-02T21:41:16.462Z
Updated: 2026-02-04T16:54:14.291Z

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

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

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

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

Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a allows remote unauthenticated users to bypass web authentication and authorization.

Published: 2023-08-31T00:54:27.046Z
Updated: 2025-02-13T16:50:08.711Z

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.

Published: 2023-08-31T00:43:39.805Z
Updated: 2025-02-13T16:50:08.160Z

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

Published: 2024-11-21T03:26:58.406Z
Updated: 2024-11-21T17:54:10.574Z

Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled.

Published: 2024-11-21T03:04:52.786Z
Updated: 2024-11-21T18:01:26.562Z

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.

Published: 2024-11-21T01:51:59.741Z
Updated: 2024-11-21T18:01:26.445Z

Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095.

Published: 2024-11-21T01:43:54.749Z
Updated: 2024-11-21T18:01:26.337Z

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.

Published: 2024-11-21T01:36:30.175Z
Updated: 2024-11-21T18:01:26.215Z

An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh passwords in filetansfer.log in debug mode. To exploit this vulnerability, the attacker would need to have valid user credentials and turn on debug mode.

Published: 2022-05-09T16:33:41.000Z
Updated: 2024-08-03T05:48:37.343Z