SANnav versions exposes Kafka in the wan interface.

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

Insecure access controls on internal service ports in Brocade SANnav versions before 3.0.1a allow local, non-administrative host users to communicate directly with backend…

Unauthenticated remote command injection in the Brocade SANnav orchestrator HTTP service

Insufficient input sanitization of shell metacharacters in Brocade SANnav before 3.0.1a

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

Improper handling of sensitive data during IPsec policy creation and modification in Brocade SANnav before 3.0.1.a

Plaintext exposure of sensitive authentication data in SANnav discovery service log files

Incomplete log sanitization during bulk IPsec policy collection in Brocade SANnav before 3.0.1a

supply-chain attack risk

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

SQL queries with sensitive information printed in logs with Brocade SANnav before 3.0

Weak Key-exchange algorithms

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

Logic flaw in SANnav Java cache key handling object comparison handling

Information exposure vulnerability in the job scheduling component of SANnav before 3.0.1a

Plain password is generated in the audit logs while executing update-reports-purge-settings.sh script with Brocade SANnav before 2.4.0a

Plain text pbe key visible in audit log during Brocade SANnav migration from 2.4.0a to 3.0.0

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.

Incomplete property masking in the SANnav logging subsystem

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 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

An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive…

Plaintext Switch admin login password is seen in Brocade SANnav support save

Brocade SANnav DataBase plaintext password is logged in failover logs (CVE-2025-12680)

Brocade Fabric OS switch passwords when debugging is enabled

configuration secrets are logged in support-save

Brocade SANnav contains hardcoded TLS keys used by Docker