CVE-2024-10403
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 versions before 8.2.3e2, versions 9.0.0 through 9.2.0c, and 9.2.1 through 9.2.1a can capture the SFTP/FTP server password used for a firmware download operation initiated by SANnav or through WebEM in a weblinker core dump that is later captured via supportsave.
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 · high confidenceIn affected Brocade Fabric OS versions, SFTP/FTP credentials used during firmware download operations (initiated by SANnav or through WebEM) are written in plaintext to weblinker core dumps. These core dumps are then collected by the supportsave utility, allowing an attacker with access to support bundles to recover the password.
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.0c1>= 9.2.1, < 9.2.1a1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Fabric OS versionRun the command 'version' or 'fosconfig --show' to display the installed Fabric OS versionAffected if The version is earlier than 9.2.0c1, OR is 9.2.1 through 9.2.1a (9.2.1a1 not yet applied)
-
Identify supportsave bundle locationLocate the directory where supportsave outputs are stored (typically /support or similar on the management station)Affected if Supportsave bundles exist from systems running affected Fabric OS versions
-
Search for weblinker core dump filesInspect supportsave bundles for files named 'core*' or similar in weblinker-related directoriesAffected if Core dump files are present in the supportsave output and were generated during firmware download operations using SFTP/FTP credentials
Your environment is affected if the Fabric OS version falls in the range < 9.2.0c1 or >= 9.2.1 and < 9.2.1a1, and firmware downloads using SFTP/FTP have been performed, creating core dumps that may now reside in supportsave bundles.
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.0c19.2.1a1
Upgrade Fabric OS to version 8.2.3e2, 9.2.1b, or later. Treat supportsave outputs as sensitive and restrict access to authorized personnel only.
9.2.1a1 or later (or 9.2.0c1 for the 9.2.0 branch)
- 1. Identify the current Fabric OS version by running 'firmwareShow' or checking SANnav inventory
- 2. Schedule a maintenance window as firmware upgrade requires fabric-wide coordination
- 3. Download the fixed Fabric OS release (9.2.1a1 or later) from Broadcom support portal at support.broadcom.com
- 4. Upload the firmware to the switch using 'firmwareDownload' command or via SANnav
- 5. Confirm the upgrade was successful by running 'firmwareShow' to verify the new version is running
- 6. Verify the fix is applied by confirming the version is >= 9.2.1a1 (or >= 9.2.0c1 for the 9.2.0 branch)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10403 — 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-10403 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