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

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

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

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

Incomplete property masking in the SANnav logging subsystem

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)