EUVD-2026-86469
GHSA-678q-3q5m-3p8x
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Reading local application logs/support bundles requires low-privileged local or authenticated access, so AV:L and PR:L; high-value cleartext credentials give C:H with no integrity or availability impact.
Primary rating from Vendor (brocade).
CVSS VectorVendor: brocade
Lifecycle Timeline
1DescriptionCVE.org
An information exposure vulnerability in the job scheduling component of SANnav allows sensitive credentials to be written to application logs in plain text. When scheduled support save jobs or related operational tasks are executed, sensitive parameters including external server passwords and archive protection keys are logged without proper masking. A local or authenticated user with access to application logs or support bundles can view these cleartext credentials, potentially leading to unauthorized access to remote backup targets or protected archives.
AnalysisAI
Cleartext credential exposure in the job scheduling component of Brocade SANnav causes external server passwords and archive protection keys to be written unmasked into application logs and generated support bundles whenever scheduled support-save or related operational jobs execute. An authenticated, low-privileged user who already has read access to those logs or bundles can harvest the credentials and potentially reuse them against remote backup targets or protected archives. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
No credit card · 7-day full trial
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the attacker to already possess read access to SANnav application logs or a generated support bundle, and the leaked secrets are only present after scheduled support-save jobs or related operational tasks have actually run with external server passwords / archive protection keys configured. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine but LOW-priority information-disclosure issue, not a network-facing critical flaw. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No fix version is identified in the provided intelligence, so patch status is not confirmed from available data; consult the Broadcom/Brocade advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38999 for the current fixed build and apply it as soon as the vendor publishes the target release. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Incomplete log sanitization in Brocade SANnav before 3.0.1a causes extension switch IPsec pre-shared keys (PSKs) to be w
In Brocade SANnav before Brocade SANnav 2.2.0, multiple endpoints associated with Zone management are susceptible to SQL
A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an
Brocade SANnav deployments running versions before 3.0.1a expose backend management service ports without adequate acces
Command injection in the Brocade SANnav CLI scripting component lets an authenticated user who already holds command-exe
Pre-shared keys used for IPsec tunnel configuration are recorded in cleartext inside application log files by Brocade SA
Plaintext disclosure of administrative switch credentials and live session tokens in Brocade SANnav discovery-service lo
A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries
In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored usin
In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Sup
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas
A vulnerability in update-reports-purge-settings.sh script logging for Brocade SANnav before 2.4.0a could allow the coll
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today