CVE-2020-15374
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 · uneditedRest API in Brocade Fabric OS v8.2.1 through v8.2.1d, and 8.2.2 versions before v8.2.2c is vulnerable to multiple instances of reflected input.
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 confidenceThe Brocade Fabric OS REST API contains multiple reflected Cross-Site Scripting (XSS) vulnerabilities where user-supplied input is returned in API responses without proper sanitization. An unauthenticated attacker could craft malicious requests containing JavaScript that would execute in the context of a user's browser when they interact with the API.
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= 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.2cCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Brocade Fabric OS installationRun 'version' or 'firmwareShow' command on the device CLI to confirm Fabric OS is installedAffected if The device is not running Broadcom/Brocade Fabric Operating System
-
Check Fabric OS versionExecute 'version' command and note the exact version string (e.g., 8.2.1, 8.2.2a, etc.)Affected if The installed version matches any of: 8.2.1, 8.2.1a, 8.2.1b, 8.2.1c, 8.2.1d, 8.2.2, 8.2.2a, 8.2.1a1, 8.2.2b, or 8.2.2c
-
Confirm REST API is enabledCheck if REST API endpoints are accessible via HTTP/HTTPS (e.g., attempt GET to common API paths like /rest or review 'webServer' configuration via CLI)Affected if The REST API interface is enabled and reachable over the network
-
Test for reflected XSS in API parametersSend a crafted GET request to a REST API endpoint with a test XSS payload in a parameter (e.g., ?param=<script>alert(1)</script>) and inspect if the payload is reflected verbatim in the response body without encodingAffected if User-supplied input from API request parameters is returned in the response without HTML encoding or sanitization
A system is affected if it runs Broadcom Fabric OS versions 8.2.1 through 8.2.2c with the REST API enabled, and the API reflects unsanitized user input in responses.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to Brocade Fabric OS v8.2.2c or later to obtain the vendor patch. If immediate patching is not feasible, implement input validation and output encoding on all REST API endpoints as a compensating control.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15374 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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