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

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

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

Weak TLS Ciphers on Brocade SANnav port 443 & 18082

Protection mechanisms

Brocade SANnav encryption key is logged in the debug logs

Clear text password seen in switch-asset-collectors-mw in Brocade SANnav supportsave

A vulnerability in Brocade SANnav before 3.0.1 can have the Brocade Fabric OS switch admin password captured in plaintext within a memory swap file on the server hosting the…