CVE-2025-58379
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBrocade Fabric OS before 9.2.1 has a vulnerability that could allow a local authenticated attacker to reveal command line passwords using commands that may expose higher privilege sensitive information by a lower privileged user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBrocade Fabric OS before version 9.2.1 contains a local privilege escalation vulnerability where an authenticated user with lower privileges can execute certain command line commands that expose sensitive information, specifically passwords, belonging to higher-privileged accounts. This is a vertical privilege escalation via command injection or improper permission handling in the CLI.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Fabric OS versionExecute the CLI command to display the Fabric OS version (typically 'version' or 'firmwareShow' command). Compare the displayed version number to the vulnerable range of versions prior to 9.2.1.Affected if The installed version is below 9.2.1 (e.g., 9.2.0, 9.1.x, 9.0.x, earlier releases).
-
Identify all CLI user accounts and their privilege rolesUse the CLI to list all user accounts and their assigned privilege levels (typically via 'userConfig --show' or similar user management commands).Affected if Multiple user accounts exist with different privilege levels, and any account with lower privileges can access sensitive commands.
-
Audit CLI command execution logs for privilege escalation attemptsReview system logs, audit logs, or CLI history for commands that may have been used to access higher-privileged account information, especially commands that expose passwords or user credentials.Affected if Logs show commands executed by lower-privileged users that accessed sensitive information belonging to higher-privileged accounts.
-
Verify CLI permission controls on sensitive commandsExamine the CLI configuration to determine which commands are accessible to each privilege level. Check if commands exposing account passwords are restricted to appropriate privilege levels.Affected if Lower-privileged users can execute commands that reveal or manipulate credentials of higher-privileged accounts.
-
Review recent authentication and command activityCheck authentication logs and session records for any unauthorized or unusual command execution patterns, particularly involving credential disclosure.Affected if There are records of lower-privileged users successfully executing commands that exposed higher-privileged account passwords.
The environment is affected if the Fabric OS version is below 9.2.1 and lower-privileged users can access commands that expose passwords or sensitive information of higher-privileged accounts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2.1
Upgrade Brocade Fabric OS to version 9.2.1 or later to obtain the patch. Until then, restrict CLI access to only trusted personnel and monitor for unauthorized access attempts.
Fabric OS 9.2.1 or later
- Verify current Fabric OS version using 'firmwareShow' command
- Download Fabric OS 9.2.1 or later from support.broadcom.com
- Review Brocade Fabric OS upgrade documentation for your specific hardware platform
- Follow standard Fabric OS upgrade procedure: backup configuration, upload new firmware, verify integrity, and reboot
- Confirm upgrade success using 'firmwareShow' and verify version is 9.2.1 or later
- Verify the vulnerability is resolved by confirming lower privileged users can no longer access higher privilege sensitive information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58379 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data