CVE-2025-12679: Plain text pbe key visible in audit log during Brocade SANnav migration from 2.4.0a to 3.0.0
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-12679?
CVE-2025-12679 is classified as a high severity vulnerability due to the exposure of sensitive key material in plaintext.
How do I fix CVE-2025-12679?
To mitigate CVE-2025-12679, upgrade Brocade SANnav to version 2.4.0b or later immediately.
What is the risk associated with CVE-2025-12679?
The risk associated with CVE-2025-12679 includes potential unauthorized access to sensitive data due to exposure of the PBE key in audit logs.
Who is affected by CVE-2025-12679?
CVE-2025-12679 affects all users of Brocade SANnav versions between 2.4.0a and 3.0.0.
What does CVE-2025-12679 expose?
CVE-2025-12679 exposes the Password-Based Encryption (PBE) key in plaintext, compromising the confidentiality of encrypted data.