CVE-2025-12679: high-severity vulnerability in Brocade SANnav
Plain text pbe key visible in audit log during Brocade SANnav migration from 2.4.0a to 3.0.0
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.2%
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.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H
Affected products
Brocade · SANnavRelated CVEs — Brocade SANnav
In the same product, most dangerous first.
CVE-2023-31424HIGHWeb authentication and authorization bypassEPSS 0.9%CVE-2022-43936MEDIUMBrocade Fabric OS switch passwords when debugging is enabledEPSS 0.8%CVE-2026-82370HIGHUnauthenticated remote command injection in the Brocade SANnav orchestrator HTTP serviceEPSS 0.6%CVE-2022-43937MEDIUMBrocade SANnav Information Disclosure VulnerabilityEPSS 0.5%CVE-2022-43934MEDIUMWeak Key-exchange algorithmsEPSS 0.5%CVE-2026-82369HIGHInsufficient input sanitization of shell metacharacters in Brocade SANnav before 3.0.1aEPSS 0.4%