dbcve.org
Fabric Operating SystemOperating system · Broadcom

CVE-2020-15373

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
Multiple buffer overflow vulnerabilities in REST API in Brocade Fabric OS versions v8.2.1 through v8.2.1d, and 8.2.2 versions before v8.2.2c could allow remote unauthenticated attackers to perform various attacks.

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

Multiple buffer overflow vulnerabilities in the REST API of Brocade Fabric OS versions v8.2.1 through v8.2.1d and v8.2.2 before v8.2.2c allow remote unauthenticated attackers to potentially execute arbitrary code or cause denial of service via specially crafted API requests.

MitigationUpgrade to Fabric OS v8.2.1e or v8.2.2c or later. If immediate patching is not feasible, restrict network access to the management interface and disable unauthenticated API access.

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.1= 8.2.1a= 8.2.1b= 8.2.1c= 8.2.1d= 8.2.2= 8.2.2a= 8.2.2a1= 8.2.2b= 8.2.2c

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. Identify the Fabric OS version
    Log into the fabric switch CLI and run the 'version' or 'firmwareShow' command to display the installed Fabric OS version
    Affected if The displayed version matches 8.2.1, 8.2.1a, 8.2.1b, 8.2.1c, 8.2.1d, 8.2.2, 8.2.2a, 8.2.2a1, 8.2.2b, or 8.2.2c (versions before 8.2.1e or 8.2.2c)
  2. Confirm REST API is accessible
    Attempt to reach the REST API endpoint on the management interface (typically port 443 or 8080) using a browser or HTTP client
    Affected if The REST API responds to requests, indicating it is enabled and reachable
  3. Verify unauthenticated API access is permitted
    Send an unauthenticated request to a REST API endpoint (such as GET /rest/login) without providing credentials
    Affected if The API accepts and processes the request without requiring authentication
  4. Assess management interface network exposure
    Review the switch network configuration to determine if the management interface is accessible from untrusted networks
    Affected if The management interface with REST API is exposed to the internet or untrusted VLANs

You are affected if your Fabric OS version is 8.2.1 through 8.2.1d or 8.2.2 through 8.2.2b (before 8.2.2c) AND the REST API is enabled and accessible, especially without authentication from your network.

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 to Fabric OS v8.2.1e or v8.2.2c or later. If immediate patching is not feasible, restrict network access to the management interface and disable unauthenticated API access.

Recommended fix High confidence

Fabric OS v8.2.2c or later

  1. 1. Identify the current Fabric OS version by running 'version' or 'firmwareShow' command
  2. 2. Download the fixed firmware version v8.2.2c or later from Broadcom support portal (support.broadcom.com)
  3. 3. Verify the firmware integrity using checksums provided by Broadcom
  4. 4. Back up the current configuration using 'configupload' command
  5. 5. Install the firmware using 'firmwaredownload' command or through Web Tools
  6. 6. Verify the upgrade was successful by checking the new version with 'version' command
  7. 7. Confirm all services are operational after reboot
Caveat Review release notes for any configuration or feature changes between your current version and v8.2.2c; some legacy REST API behaviors may have been modified for security

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

Fix this in Fabric Operating System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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