dbcve.org
Fabric Operating SystemOperating system · Broadcom

CVE-2020-15371

CRITICAL · 9.8 CVSS v3.1 Published 2020-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Brocade Fabric OS versions before Brocade Fabric OS v9.0.0, v8.2.2c, v8.2.1e, v8.1.2k, v8.2.0_CBN3, contains code injection and privilege escalation vulnerability.

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

Brocade Fabric OS contains a code injection and privilege escalation vulnerability that allows authenticated attackers to inject arbitrary code and escalate privileges to gain higher access rights on the fabric management interface.

MitigationUpgrade Brocade Fabric OS to v9.0.0 or later, or to one of the patched versions v8.2.2c, v8.2.1e, v8.1.2k, or v8.2.0_CBN3 to remediate the 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:= 8.0.0= 8.0.1= 8.0.1a= 8.0.1b= 8.0.2= 8.0.2a= 8.0.2b= 8.0.2c= 8.0.2d= 8.0.2f= 8.1.0= 8.1.0a

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
    Log into the fabric management interface (via CLI using admin credentials or web GUI) and run the command 'version' or 'firmwareShow' to display the installed firmware version
    Affected if The displayed version matches any of the following: 8.0.0, 8.0.1, 8.0.1a, 8.0.1b, 8.0.2, 8.0.2a, 8.0.2b, 8.0.2c, 8.0.2d, 8.0.2f, 8.1.0, or 8.1.0a
  2. Verify administrative access exists
    Confirm you have valid credentials for the fabric management interface (admin or root-level access) by logging in via SSH, console, or web GUI
    Affected if You can authenticate to the fabric management interface with any administrative account
  3. Check for unauthorized access indicators
    Review audit logs using 'auditShow' command or check for unexpected accounts or configuration changes in the fabric management interface
    Affected if Unexpected user accounts, scripts, or configuration changes are present that you did not create

You are affected if your Brocade Fabric OS version matches one of the listed vulnerable versions (8.0.0 through 8.1.0a) and you have an authenticated user with access to the fabric management interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Brocade Fabric OS to v9.0.0 or later, or to one of the patched versions v8.2.2c, v8.2.1e, v8.1.2k, or v8.2.0_CBN3 to remediate the vulnerability.

Recommended fix Moderate confidence

Upgrade to Fabric OS v9.0.0 or later (or at minimum v8.2.2c, v8.2.1e, v8.1.2k, or v8.2.0_CBN3 as listed in the official description)

  1. 1. Identify the current Fabric Operating System version using 'version' command or via management interface
  2. 2. Review Broadcom/SAN documentation for upgrade procedures specific to your hardware platform
  3. 3. Create a full backup of the current Fabric OS configuration
  4. 4. Download the appropriate fixed version from Broadcom support portal (v9.0.0 or later, or v8.2.2c/v8.2.1e/v8.1.2k/v8.2.0_CBN3)
  5. 5. Schedule maintenance window as upgrades may cause brief Fabric disruption
  6. 6. Upload the firmware to the switch using 'firmwareDownload' or equivalent command
  7. 7. Verify successful installation with 'version' command post-upgrade
  8. 8. Confirm all Fabric services are operational and security controls are functioning
Caveat Review release notes for potential Fabric behavior changes or deprecated features between current and target version

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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