Weak TLS Ciphers on Brocade SANnav OVA SSH port 22

SANnav versions exposes Kafka in the wan interface.

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

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

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout

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

RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration…

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

A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID

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

supply-chain attack risk

In Brocade SANnav before 3.0.0a, an SQL Injection vulnerability in various external API inventories have a vulnerability that allows an authenticated attacker to inject malicious…

The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect local authentication flaw

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

Weak Key-exchange algorithms

Syslog traffic sent in clear-text

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

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

Encryption key is stored in the DR log files

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…

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…

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…

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…

Docker implementation in Brocade SANnav is missing Audit Rules.

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

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

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

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

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

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

Brocade SANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords in plaintext

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

Insecure backup

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

A path traversal vulnerability affects the The Zone Alias Import flow feature in Brocade SANnav before 3.0.0a

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files

Brocade SANnav has weak encryption in internal SSH ports

Brocade SANnav Information Disclosure Vulnerability

Insecure file permission setting that makes files world-readable

Insertion of Sensitive Information into Brocade SANnav Log File

Clear text storage of sensistive information by manipulating command variables

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…

Brocade SANnav versions before v2.0, logs plain text database connection password while triggering support save

The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' logging level; which could allow a local…

Weak TLS Ciphers on Brocade SANnav port 443 & 18082

Protection mechanisms

Brocade SANnav encryption key is logged in the debug logs

Brocade Fabric OS switch passwords when debugging is enabled

Brocade SANnav before v2.2.1 logs usernames and encoded passwords in debug-enabled logs