CVE-2023-31426
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 · uneditedThe Brocade Fabric OS Commands “configupload” and “configdownload” before Brocade Fabric OS v9.1.1c, v8.2.3d, v9.2.0 print scp, sftp, ftp servers passwords in supportsave. This could allow a remote authenticated attacker to access sensitive information.
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 Brocade Fabric OS, the 'configupload' and 'configdownload' commands that transfer configuration files to/from remote SCP, SFTP, or FTP servers store server credentials. These passwords are being written in plaintext to the supportsave output, which can be accessed by remote authenticated attackers. This allows credential harvesting for further attacks against the file transfer infrastructure.
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< 8.2.3d>= 9.0.0, < 9.1.1cCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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.
-
Check Fabric OS versionRun 'version' or 'firmwareShow' command on the Fabric OS device to obtain the installed version string.Affected if The version is below 8.2.3d, or is 9.0.0 through 9.1.1b (any version < 9.1.1c, excluding 8.2.3d and above 9.1.1c).
-
Identify supportsave archivesLocate any supportsave output files or archives on the device, on external servers used for file transfers, or in any backup storage where supportsave data has been stored.Affected if Supportsave archives exist from a time period after configupload or configdownload commands were used.
-
Inspect supportsave for plaintext credentialsExtract the supportsave archive and search the contents (particularly configuration files or logs) for plaintext passwords associated with SCP, SFTP, or FTP server credentials. Look for patterns like 'password=' or actual password strings in files named similarly to config, upload, or transfer related outputs.Affected if Plaintext passwords for remote file transfer servers are found in the supportsave output.
-
Review command logs for configupload/configdownload usageCheck system logs, command history, or audit logs for any executed 'configupload' or 'configdownload' commands that specify remote server credentials.Affected if These commands have been run and the resulting supportsave output has not been secured.
A user is affected if their Fabric OS version falls within the vulnerable range AND they have used configupload/configdownload, making their server credentials potentially readable in supportsave output.
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 · scoped8.2.3d9.1.1c
Upgrade to Brocade Fabric OS v9.1.1c, v8.2.3d, v9.2.0 or later to patch the vulnerability. In the interim, strictly control access to supportsave output and rotate any credentials that may have been exposed.
Fabric OS v8.2.3d (or later 8.x) / v9.1.1c (or later 9.1.x) / v9.2.0 (or later 9.2.x)
- 1. Identify the current Fabric OS version running on the affected Brocade switch
- 2. Schedule a maintenance window for the upgrade following change management procedures
- 3. Download the appropriate fixed Fabric OS version from Broadcom support portal (support.broadcom.com) - choose v8.2.3d or later for 8.x systems, or v9.1.1c or later for 9.x systems
- 4. Follow Broadcom's documented Fabric OS upgrade procedure in the administration guide
- 5. After upgrade, verify the version using 'version' command to confirm the fix is applied
- 6. Test configupload/configdownload functionality to ensure operational integrity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31426 — 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-2023-31426 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