Fabric Operating SystemOperating system · Broadcom

CVE-2023-31429

MEDIUM · 5.5 CVSS v3.1 Published 2023-08-01
Fix available
A fix is available. Upgrade to 9.1.1c 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
Brocade Fabric OS before Brocade Fabric OS 9.1.1c, 9.2.0 contains a vulnerability when using various commands such as “chassisdistribute”, “reboot”, “rasman”, errmoduleshow, errfilterset, hassiscfgperrthreshold, supportshowcfgdisable and supportshowcfgenable commands that can cause the content of shell interpreted variables to be printed in the terminal.

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

Brocade Fabric OS contains an information disclosure vulnerability where multiple privileged commands (chassisdistribute, reboot, rasman, errmoduleshow, errfilterset, hassiscfgperrthreshold, supportshowcfgdisable, supportshowcfgenable) inadvertently print shell interpreted variables to the terminal output, potentially exposing environment variables, paths, or other sensitive system information.

MitigationUpgrade to Brocade Fabric OS 9.1.1c or later, or 9.2.0 and later to remediate this vulnerability.

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:< 9.1.1c

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. Identify Fabric OS version
    Run 'version' or 'switchname' command to display the Fabric OS version installed on the Brocade switch
    Affected if The displayed version is earlier than 9.1.1c (for example 9.1.0, 9.0.x, 8.x, etc.)
  2. Verify affected command availability
    Confirm you have administrative/privileged access to the switch CLI and can execute privileged commands such as chassisdistribute, reboot, rasman, errmoduleshow, errfilterset, hassiscfgperrthreshold, supportshowcfgdisable, or supportshowcfgenable
    Affected if You have privileged access and these commands are available on your system
  3. Test for shell variable leakage in command output
    Execute one of the affected privileged commands (e.g., 'chassisdistribute' or 'rasman') and carefully examine the terminal output for any unexpanded shell variables, environment variable names (like PATH, HOME, USER), dollar signs with variable names, or other system information that should not be displayed
    Affected if The output contains literal shell variables, environment variable references, or system paths that indicate the shell interpreted the output rather than displaying static text

You are affected if your Fabric OS version is earlier than 9.1.1c AND you can execute the listed privileged commands which expose shell variables in their output.

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 9.1.1c or later
Fixed in 9.1.1c
Interim mitigation

Upgrade to Brocade Fabric OS 9.1.1c or later, or 9.2.0 and later to remediate this vulnerability.

Recommended fix High confidence

Fabric OS 9.1.1c or later

  1. Upgrade Fabric Operating System to version 9.1.1c or later
  2. Verify the upgrade was successful by checking the firmware version using the 'version' command
  3. Test the affected commands (chassisdistribute, reboot, rasman, errmoduleshow, errfilterset, hassiscfgperrthreshold, supportshowcfgdisable, supportshowcfgenable) to confirm the vulnerability is resolved

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

Fix this in Fabric Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31429 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31429 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