Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain access to SANnav logs or supportsave bundle
-
ExploitLocate encoded passwords and auth tokens in files
-
ExecutionDecode the reversibly-encoded credentials
-
ImpactReuse credentials against SANnav and managed SAN devices
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Secure storage of sensitive data
|
| Exploitation Conditions | Exploitation requires the attacker to obtain SANnav log files or, specifically, the SANnav supportsave diagnostic bundle, which records encoded (reversible, not hashed) passwords and authentication tokens. The description scopes the attacker as 'authenticated ... with access to the log file,' so the gating prerequisite is file-level access to these artifacts rather than an open network request; this is reinforced by the CVSS AV:A (adjacent) and UI:P (passive user interaction, e.g. a supportsave being generated/shared). Limiting factors: affected only in SANnav versions before 2.4.0b and 3.0.0; exploitation depends on the attacker acquiring the log or supportsave output (often exported and handed to support), which is the primary real-world barrier. Note the input vector's PR:N contradicts the description's authenticated-attacker wording - confirm with the vendor. |
| Impact | The input assigns a CVSS 4.0 base score of 8.2 (High) with vector AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N. The high score is driven by high confidentiality impact (VC:H) plus a subsequent-system confidentiality impact (SC:H), reflecting that the leaked passwords and authentication tokens can be reused against other managed SAN systems. However, there is a direct conflict between the CVSS vector and the description: the vector encodes PR:N (no privileges required), yet the description explicitly states the flaw 'could allow an authenticated attacker with access to the log file' to access the passwords - verify the true privilege requirement with Brocade, as the practical prerequisite appears to be access to log/supportsave files rather than truly unauthenticated network access. The vector's AV:A (adjacent) and UI:P (passive user interaction) further imply the credentials are exposed via artifacts (logs, supportsave diagnostic bundles) rather than a direct remote request. No EPSS score, KEV listing, or public POC is present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: a credible credential-exposure issue (CWE-922, insecure storage) that is genuinely dangerous because passwords are merely 'encoded' (reversible) rather than hashed, but real-world risk is gated by the need to obtain log or supportsave files - making this a patch-soon priority rather than an emergency, and lower in practical urgency than the raw 8.2 suggests. |
| Exploit ScenarioDerived | An attacker who obtains a SANnav supportsave diagnostic bundle or log files - for example an insider, or someone receiving bundles routinely exported and shared with vendor support - locates the encoded passwords and authentication tokens written to those files and decodes them. The recovered credentials can then be used to authenticate to SANnav and the managed fabric. No public POC is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Information disclosure in Brocade SANnav before 2.4.0b and 3.0.0 occurs because the product writes encoded passwords and authentication tokens to log files, including the SANnav supportsave diagnostic bundle. An attacker who gains access to those logs or the supportsave output can recover secrets and potentially reuse them, though the description frames this as requiring an authenticated attacker with file-level access and the assessed vector reflects a local/authenticated prerequisite; the input CVSS 4.0 vector lists PR:N, a discrepancy that should be confirmed with the vendor. No public exploit identified at time of analysis, and no CISA KEV confirmation was provided.
RemediationAI
Upgrade to Brocade SANnav 2.4.0b or later for 2.4.x installations, or to 3.0.0 or later for 3.x installations, as specified by the vendor advisory at https://support.broadcom.com/external/content/SecurityAdvisories/0/37933. If immediate patching is not possible, restrict access to SANnav log files and supportsave diagnostic bundles to the minimum necessary personnel, and treat exported supportsave files as sensitive credentials because the stored passwords and tokens are reversibly encoded rather than hashed. Rotate any passwords or authentication tokens that may have been captured in logs or shared diagnostics, review log retention and support-case handling procedures, and monitor for unauthorized access to SANnav log storage. These compensating controls reduce exposure but do not eliminate the underlying weakness, so upgrading remains the primary fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is classified as CWE-922 (Insecure Storage of Sensitive Information), and the core weakness is that SANnav logs and the supportsave diagnostic bundle record passwords and authentication tokens using reversible encoding rather than one-way hashing. That means anyone who obtains the log file or supportsave archive can decode the values and recover credentials or session tokens. The affected CPE entry is cpe:2.3:a:brocade:brocade_sannav:*:*:*:*:*:*:*:*, which broadly identifies the product, while the advisory scopes the flaw to versions before 2.4.0b and 3.0.0. The input assigns CVSS 4.0 score 8.2 with vector CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N, but the independent assessment uses CVSS 3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, reflecting a local, authenticated/file-access prerequisite rather than an unauthenticated remote condition; this discrepancy should be resolved with the vendor. The disclosure does not directly grant code execution or integrity impact, but it can expose high-value credentials that enable lateral movement or further compromise of the SAN management environment.
Know when Brocade Sannav gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Exploitation requires authenticated access to read SANnav log/supportsave files (PR:L, AV:L); leaked credentials enable access to other managed systems (S:C); only confidentiality is affected (C:H, I/A:N).
Primary rating from Vendor (brocade).
CVSS VectorVendor: brocade
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.
Executive ViewAI
Brocade SANnav, the management platform used to administer SAN fabrics, writes encoded administrative passwords and authentication tokens into its own log files and the supportsave diagnostic bundle, meaning anyone who can read those artifacts can recover credentials that unlock the storage network. Because SANnav credentials typically grant broad control over fabric switches, zones, and attached storage, a single exposed log or a shared support bundle could enable lateral movement into the most sensitive tier of the data center. The vendor has not released a patch, so leadership should treat the exposure as an unmitigated credential-hygiene risk requiring immediate controls on who can access SANnav logs and bundles.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict file-system access to SANnav logs and supportsave bundles to the minimum necessary administrators; stop or sanitize external transmission of diagnostic bundles; rotate all SANnav passwords and authentication tokens that may have been logged; enable encryption and short retention for log archives; and monitor for unauthorized access to log directories. Note that no public exploit identified at time of analysis, but the exposure is a credential-recovery risk once any read access is obtained.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Brocade Sannav
View allRADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be
A vulnerability in Brocade SANnav exposes Kafka in the wan interface. Rated critical severity (CVSS 9.8), this vulnerabi
Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appl
Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a allows remote unauthenticated users to bypass web
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write acce
Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. Rated high severity (CVSS 8.6), this vulnera
A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID.
Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obt
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the B
Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. Rated high severity (CVSS 8
A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. Rated high severity (CVSS 8.2), this vulnerability is
EUVD-2026-94756
GHSA-vrg4-pprr-h7xv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB