CVE-2023-3489
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 firmwaredownload command on Brocade Fabric OS v9.2.0 could log the FTP/SFTP/SCP server password in clear text in the SupportSave file when performing a downgrade from Fabric OS v9.2.0 to any earlier version of Fabric OS.
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 confidenceThe firmwaredownload command on Brocade Fabric OS v9.2.0 logs FTP/SFTP/SCP server passwords in clear text to SupportSave files when performing a downgrade from v9.2.0 to any earlier Fabric OS version, exposing authentication credentials in plaintext.
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.0CVSS 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.
-
Confirm Fabric OS versionRun 'firmwareShow' or check the system version to determine if the installed Fabric OS is version 9.2.0 exactlyAffected if The installed version is exactly 9.2.0; versions before or after are not affected by this specific CVE
-
Check for downgrade operationsReview history of firmwaredownload command usage, specifically looking for downgrade operations from v9.2.0 to earlier versions using the --downgrade flag or equivalent syntaxAffected if A downgrade from v9.2.0 to any earlier Fabric OS version was performed using the firmwaredownload command
-
Locate SupportSave filesAccess the SupportSave directory or archive location (typically /support or similar on the fabric device) where diagnostic files are storedAffected if SupportSave files exist from sessions where a downgrade from v9.2.0 was performed
-
Search for plaintext credentialsExamine SupportSave files using grep or text search for patterns matching FTP, SFTP, or SCP server passwords in clear text; look for password strings in proximity to protocol identifiersAffected if Plaintext passwords for FTP, SFTP, or SCP servers appear in any SupportSave file content
A system is affected only if it is running Fabric OS v9.2.0 AND a downgrade to an earlier version was performed using firmwaredownload, resulting in plaintext credentials present in SupportSave files.
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.
From vendor dataAvoid downgrading from Fabric OS v9.2.0 when possible, and ensure SupportSave files containing credentials are securely stored or deleted after troubleshooting. Apply vendor-provided patches when available.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3489 — 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-3489 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