Broadcom Brocade any version

SQL injection in JDBC Appender in Apache Log4j V1

Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability.

Web authentication and authorization bypass

hard-coded credentials in the documentation that appear as the appliance root password

SANnav versions exposes Kafka in the wan interface.

Weak TLS Ciphers on Brocade SANnav OVA SSH port 22

RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.

Deserialization of untrusted data in JMSSink in Apache Log4j 1.x

A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. The vulnerability could allow a remote attacker to bypass the authentication process.

A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID. The vulnerability is due to an insufficiently random session ID for several post-authentication actions in the SANnav portal.

Docker implementation in Brocade SANnav is missing Audit Rules.

Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save

Syslog traffic sent in clear-text

Brocade SANnav encryption key is logged in the debug logs

supply-chain attack risk

Brocade SANnav versions before v2.0 use a hard-coded password, which could allow local authenticated attackers to access a back-end database and gain privileges.

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.

SQL Table names, column names, and SQL queries are collected in DR standby Supportsave

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.

Weak Key-exchange algorithms

Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.).

Identical SSH keys utilized inside the OVA image (CVE-2024-29960)

Brocade SANnav before v2.3.1, v2.3.0a uses weak encryption

Encryption key is stored in the DR log files

TLS/SSL weak message authentication code ciphers are added by default for port 18082

Encryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node.

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.

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.

Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password ‘passw0rd’ if a password is not provided for PostgreSQL at install-time.

By default, SANnav OVA is shipped with root user login enabled (CVE-2024-2859)

Weak TLS Ciphers on Brocade SANnav port 443 & 18082

Brocade Fabric OS switch passwords when debugging is enabled

Insecure backup

Daily Data Dump Collector logs database password in cleartext when running docker exec commands (CVE-2025-6392)

Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files

cleartext password in supportsave logs when a user schedules a switch Supportsave from Brocade SANnav

Storage of clear text password in Brocade SANnav

In Brocade SANnav before v2.31 and v2.3.0a, it was observed that Docker instances inside the appliance have insecure mount points

Brocade SANnav Information Disclosure Vulnerability

Possible information exposure through log file vulnerability