Threat database

A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. Note: The vulnerability is only triggered during a migration and not in a new installation. The system audit logs are accessible only to a privileged user on the server. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user.

CVE-2025-12680 is a medium-severity vulnerability affecting Brocade SANnav versions prior to 2.4.0b, where database passwords are stored in plaintext within logs on the standby SANnav server after disaster recovery failover. This flaw allows a remote attacker with administrative privileges and some user interaction to access sensitive logs or supportsave files and extract database credentials. Exploitation requires authenticated admin access but can lead to credential compromise, potentially enabling further unauthorized access to SANnav-managed storage infrastructure. No known exploits are currently reported in the wild. The vulnerability impacts confidentiality primarily, with a CVSS score of 6. European organizations using affected Brocade SANnav versions should prioritize patching and restrict access to logs and supportsave files. Countries with significant enterprise storage deployments and Brocade SANnav usage, such as Germany, France, and the UK, are most likely to be affected.

EPSS 0.3%VulnerabilityBrocade#cwe-256#cwe-312Germany+2

A path transversal vulnerability in Brocade Fabric OS 9.1.0 through 9.2.2 could allow a local admin user to gain access to files outside the intended directory potentially leading to the disclosure of sensitive information. Note: Admin level privilege is required on the switch in order to exploit

Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obtained from a Brocade SANnav supportsave. An attacker with privileged access to the Brocade SANnav database could use the encryption key to obtain passwords used by Brocade SANnav.