dbcve.org
Brocade Fabric Operating SystemOperating system · Broadcom

CVE-2023-31927

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-02
Fix available
A fix is available. Upgrade to 9.1.1c or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
An information disclosure in the web interface of Brocade Fabric OS versions before Brocade Fabric OS v9.2.0 and v9.1.1c, could allow a remote unauthenticated attacker to get technical details about the web interface.

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 confidence

An information disclosure vulnerability in the web interface of Brocade Fabric OS allows remote unauthenticated attackers to obtain technical details about the web interface. This affects versions prior to v9.2.0 and v9.1.1c. The issue is exploitable without authentication, potentially revealing configuration details, version information, or implementation specifics.

MitigationApply the vendor-supplied updates (Brocade Fabric OS v9.2.0 or v9.1.1c or later) to all affected devices. If immediate patching is not possible, restrict network access to the web interface using firewall rules or access controls to limit exposure to unauthenticated attackers.

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
Brocade 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Determine Fabric OS version
    Access the switch via console or SSH and execute the command to display the Fabric OS version (typically 'version' or 'firmwareShow'). Compare the displayed version number to the affected ranges: versions prior to 9.1.1c or 9.2.0 are vulnerable.
    Affected if The installed Fabric OS version is lower than 9.1.1c (or lower than 9.2.0 if that build path is used).
  2. Confirm web interface is enabled
    Check if the web management interface (HTTP/HTTPS) is enabled on the device. This is typically configured via 'webManagement' or similar command in Fabric OS CLI.
    Affected if The web interface is enabled and accessible.
  3. Verify network accessibility
    Determine if the web interface is exposed to unauthenticated network access by checking the management IP configuration and any applied access controls or firewall rules.
    Affected if The web interface is reachable from untrusted networks without authentication barriers.

A system is affected if it runs Fabric OS version lower than 9.1.1c (or lower than 9.2.0) AND has the web interface enabled and accessible to unauthenticated attackers.

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

Apply the vendor-supplied updates (Brocade Fabric OS v9.2.0 or v9.1.1c or later) to all affected devices. If immediate patching is not possible, restrict network access to the web interface using firewall rules or access controls to limit exposure to unauthenticated attackers.

Recommended fix High confidence

Brocade Fabric OS v9.2.0 (or v9.1.1c as alternative)

  1. Identify the current Brocade Fabric OS version running on the affected device using 'version' or 'firmwareShow' command
  2. Download Brocade Fabric OS v9.1.1c or v9.2.0 (recommended) from the Broadcom support portal at support.broadcom.com
  3. Review the Fabric OS upgrade procedure in the Brocade Fabric OS Administration Guide
  4. Upload the new firmware to the switch using 'firmwareDownload' command or through the web interface
  5. Verify the upgrade was successful by checking the new version with 'version' command
  6. Confirm the vulnerability is remediated by verifying the web interface no longer exposes technical details to unauthenticated users
Caveat Review release notes for v9.2.0 for any configuration or feature changes before upgrading

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

Fix this in Brocade Fabric Operating System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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