CVE-2025-4662: Broadcom Brocade SANnav · Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affects Broadcom Brocade SANnavSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.4.0 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade Broadcom Brocade SANnav to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Broadcom Brocade SANnav | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-4662, European organizations should: 1) Upgrade Brocade SANnav to version 2.4.0a or later, where this logging behavior has been addressed. 2) Restrict and monitor administrative access to the SANnav host server VM to minimize the risk of unauthorized local access. 3) Implement strict access controls and auditing on host server audit logs to detect and prevent unauthorized viewing or tampering. 4) Avoid passing sensitive passphrases via command line arguments or temporary files; instead, use secure methods such as environment variables or protected credential stores where possible. 5) Regularly review and sanitize audit logs to remove any sensitive information inadvertently logged. 6) Employ host-based intrusion detection systems (HIDS) to monitor for suspicious access patterns to audit logs. 7) Conduct security awareness training for server administrators emphasizing the risks of sensitive data exposure through logs. These steps go beyond generic advice by focusing on securing the host environment and changing operational practices around credential handling and log management.
Description
Brocade SANnav before SANnav 2.4.0a logs plaintext passphrases in the Brocade SANnav host server audit logs while executing OpenSSL command using a passphrase from the command line or while providing the passphrase through a temporary file. 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.