Broadcom 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

Brocade SANnav has weak encryption in internal SSH ports

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 Brocade SANnav Virtual Machine (VM). This can happen when the SANnav server encounters an Out Of Memory (OOM) condition. The vulnerability could allow an authenticated admin user with access to the server hosting the SANnav to potentially view the memory swap file and access the password(s).

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

Clear text storage of sensistive information by manipulating command variables

Insertion of Sensitive Information into Brocade SANnav Log File

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