dbcve.org
Fabric Operating SystemOperating system · Broadcom

CVE-2024-29954

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-26
Fix available
A fix is available. Upgrade to 8.2.3e / 9.1.1d or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
A vulnerability in a password management API in Brocade Fabric OS versions before v9.2.1, v9.2.0b, v9.1.1d, and v8.2.3e prints sensitive information in log files. This could allow an authenticated user to view the server passwords for protocols such as scp and sftp. Detail. When the firmwaredownload command is incorrectly entered or points to an erroneous file, the firmware download log captures the failed command, including any password entered in the command line.

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 confidence

The firmwaredownload command in Brocade Fabric OS logs the entire command line including passwords when the command fails or points to an invalid file, exposing plaintext server credentials for protocols like SCP and SFTP to any authenticated user with log access.

MitigationUpgrade to the patched versions (v9.2.1, v9.2.0b, v9.1.1d, or v8.2.3e) per the vendor advisory. As a workaround, avoid entering passwords directly on the command line for firmwaredownload operations.

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
Fabric Operating SystemOperating system
Affected:< 8.2.3e>= 9.0.1, < 9.1.1d>= 9.2.0, < 9.2.0b

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Fabric OS version
    Run 'version' or 'firmwareShow' command on the Fabric OS device to retrieve the installed version number
    Affected if The version is < 8.2.3e, or >= 9.0.1 and < 9.1.1d, or >= 9.2.0 and < 9.2.0b
  2. Review system logs for firmwaredownload command failures
    Access log files (typically in /var/log/ or via 'logsink' command) and search for entries containing 'firmwaredownload' that failed or pointed to invalid files
    Affected if Log entries show the full firmwaredownload command line including plaintext passwords for SCP or SFTP protocols
  3. Check for credential exposure in audit logs
    Examine audit logs or security logs accessible to authenticated users for any firmwaredownload command attempts that failed
    Affected if Logs contain plaintext credentials (passwords) passed as command-line arguments to firmwaredownload

The environment is affected if the Fabric OS version falls within the vulnerable ranges AND logs contain plaintext credentials from firmwaredownload command invocations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.2.3e / 9.1.1d / 9.2.0b or later
Fixed in 8.2.3e9.1.1d9.2.0b
Interim mitigation

Upgrade to the patched versions (v9.2.1, v9.2.0b, v9.1.1d, or v8.2.3e) per the vendor advisory. As a workaround, avoid entering passwords directly on the command line for firmwaredownload operations.

Recommended fix Moderate confidence

Fabric OS v9.2.1 or later (or v8.2.3e for 8.x, v9.1.1d for 9.0.x-9.1.x, v9.2.0b for 9.2.0.x)

  1. 1. Identify the current Fabric OS version using the 'version' command or through the management interface.
  2. 2. Download the appropriate firmware upgrade file from Broadcom's support portal (support.broadcom.com) for your hardware platform.
  3. 3. For versions < 8.2.3e: Upgrade to Fabric OS v8.2.3e or later.
  4. 4. For versions >= 9.0.1 and < 9.1.1d: Upgrade to Fabric OS v9.1.1d or later.
  5. 5. For versions >= 9.2.0 and < 9.2.0b: Upgrade to Fabric OS v9.2.1 or later (v9.2.0b also fixes this specific issue).
  6. 6. After upgrade, verify the version using 'version' command.
  7. 7. Review new firmware download logs to confirm passwords are no longer being captured in plain text.
Caveat Review Broadcom release notes for your specific hardware platform for any compatibility notes or configuration changes required by the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fabric Operating System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29954 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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