Broadcom Brocade

Brocade SANnav has weak encryption in internal SSH ports

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

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 authenticated attacker to access sensitive information.

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

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

Protection mechanisms

Switch passwords and authorization IDs are printed in the embedded MLS DB file

Plaintext security passwords are logged in the audit logs while executing openssl cmd

Cleartext storage of sensitive information in Brocade SANnav server audit logs.

configuration secrets are logged in support-save

Brocade SANnav contains hardcoded TLS keys used by Docker