CVE-2024-29959
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 · uneditedA vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save.
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 SANnav versions before v2.3.1 and v2.3.0a contain an information disclosure vulnerability where encrypted passwords for connected Brocade Fabric OS switches are inadvertently printed in support save files generated on the SANnav Standby node. An attacker with access to these support files could obtain the encrypted password data.
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< 2.3.0aCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify SANnav versionLocate the installed version of Brocade SANnav through the administrative web interface or system commandsAffected if Version is before v2.3.1 or v2.3.0a (any version < 2.3.0a)
-
Determine if SANnav is deployed with a Standby nodeCheck the SANnav deployment configuration to confirm whether a Standby node exists in the high-availability setupAffected if A Standby node is configured in the environment
-
Locate support save files on the Standby nodeAccess the file system or support directory on the SANnav Standby node and enumerate any support save filesAffected if Support save files exist on the Standby system
-
Inspect support files for Fabric OS password dataSearch within the support save files for encrypted password strings or credential data associated with connected Fabric OS switchesAffected if Encrypted password strings for Fabric OS switches are present in the support files
Environment is affected if SANnav version is before v2.3.1 or v2.3.0a AND support save files generated on a Standby node contain encrypted Fabric OS switch credentials
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 · scoped2.3.0a
Upgrade Brocade SANnav to version 2.3.1 or later (or the patched v2.3.0a version). As a precautionary measure, consider rotating Fabric OS switch credentials after the upgrade.
Brocade SANnav v2.3.1
- 1. Back up the current Brocade SANnav configuration according to the official backup procedures
- 2. Download the SANnav v2.3.1 installation package from the Broadcom support portal at support.broadcom.com
- 3. Follow the standard SANnav upgrade procedure documented in the Brocade SANnav Installation and Upgrade Guide
- 4. Verify the upgrade was successful by logging into the SANnav web interface
- 5. Confirm the vulnerability is remediated by generating a new support save and verifying no encrypted passwords appear in the output
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-2024-29959 — 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-2024-29959 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