CVE-2021-27796
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 · uneditedA vulnerability in Brocade Fabric OS versions before Brocade Fabric OS v8.0.1b, v7.4.1d could allow an authenticated attacker within the restricted shell environment (rbash) as either the “user” or “factory” account, to read the contents of any file on the filesystem utilizing one of a few available binaries.
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 confidenceBrocade Fabric OS versions before v8.0.1b and v7.4.1d contain a file read vulnerability. Authenticated attackers with limited 'user' or 'factory' accounts operating within the restricted bash (rbash) environment can exploit certain binaries to read arbitrary files on the filesystem, enabling information disclosure beyond their intended permissions.
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< 7.4.1d>= 8.0.0, < 8.0.1bCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Fabric OS versionLog into the Fabric OS management interface (via CLI or web GUI) and run the command to display the system version, typically 'version' or 'firmwareshow'Affected if The displayed version is earlier than 7.4.1d, or is 8.0.0 or 8.0.1a (versions < 7.4.1d or >= 8.0.0 and < 8.0.1b)
-
Identify configured user accountsUse the 'userconfigshow' or 'userconfig' command to list all user accounts defined on the deviceAffected if Any account with 'user' or 'factory' role is present on the system (these are the limited privilege accounts that can exploit the flaw)
-
Verify rbash environment for limited accountsCheck the shell environment assigned to user/factory accounts using 'usershow' or similar command to confirm they operate within restricted bash (rbash)Affected if The affected accounts are configured to use the default restricted shell environment (this is the default for these account types)
-
Assess network exposure of management interfaceReview firewall rules or access control lists protecting the Fabric OS management ports (TCP 22 for SSH, TCP 80/443 for web UI)Affected if Management interfaces are accessible from untrusted networks where unauthorized individuals could obtain valid user/factory credentials
You are affected if your Fabric OS version falls in the range < 7.4.1d or >= 8.0.0 and < 8.0.1b AND you have user or factory accounts configured on the system.
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.
dbcve · scoped7.4.1d8.0.1b
Upgrade Brocade Fabric OS to v8.0.1b, v7.4.1d or later. Until the patch is applied, minimize exposure by restricting network access to management interfaces and monitoring for unauthorized access attempts using the affected accounts.
Fabric OS 7.4.1d (or newer 7.x) / 8.0.1b (or newer 8.x)
- 1. Identify the current Fabric OS version using 'version' or 'firmwareShow' command
- 2. Download the appropriate fixed version from Broadcom support portal: version 7.4.1d or higher for 7.x branch, or version 8.0.1b or higher for 8.x branch
- 3. Review Broadcom upgrade documentation and release notes for the target version
- 4. Perform a backup of the current Fabric OS configuration
- 5. Upload the firmware using 'firmwareDownload' command or Fabric OS web interface
- 6. Verify the upgrade completed successfully and the new version is running
- 7. Confirm the vulnerability is resolved by verifying the fixed binaries no longer permit arbitrary file reads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27796 — 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-2021-27796 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