dbcve.org
Fabric Operating SystemOperating system · Broadcom

CVE-2022-33185

HIGH · 7.8 CVSS v3.1 Published 2022-10-25
Fix available
A fix is available. Upgrade to 9.0.1e or later.
See remediation →
80/100
Remediation priority · High
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
Several commands in Brocade Fabric OS before Brocade Fabric OS v.9.0.1e, and v9.1.0 use unsafe string functions to process user input. Authenticated local attackers could abuse these vulnerabilities to exploit stack-based buffer overflows, allowing arbitrary code execution as the root user account.

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 confidence

Brocade Fabric OS versions prior to 9.0.1e and 9.1.0 contain multiple commands that use unsafe string functions (e.g., strcpy, sprintf) to process user input. Authenticated local attackers can trigger stack-based buffer overflows by providing oversized input to these commands, achieving arbitrary code execution with root privileges.

MitigationUpgrade Brocade Fabric OS to version 9.0.1e, 9.1.0, or later to remediate the unsafe string function vulnerabilities. Alternatively, limit local authenticated access to trusted personnel only.

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:< 9.0.1e

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Determine Fabric OS version
    Execute 'version' or 'firmwareShow' command on the Fabric OS device to retrieve the installed firmware version.
    Affected if The displayed version is earlier than 9.0.1e (for example, 9.0.1d, 9.0.0, 8.x, etc.).
  2. Verify the specific firmware build
    Check the full version string including any build numbers or letters (e.g., v9.0.1d, v9.0.1c).
    Affected if The version ends with a letter earlier than 'e' (such as 'd', 'c', 'b', 'a') or lacks the 'e' suffix entirely.
  3. Confirm local authenticated access exists
    Review user accounts and access controls on the Fabric OS device using 'userConfigShow' or similar user administration commands.
    Affected if Multiple local accounts exist beyond the default admin account, or access is not restricted to trusted personnel only.
  4. Identify exposed management interfaces
    Check if telnet, SSH, or console access is enabled and accessible using 'interfaceShow' or 'ipAddrShow'.
    Affected if The management interfaces are reachable by untrusted users who possess valid local credentials.

A user is affected if their Fabric OS version is below 9.0.1e and they have or could have local authenticated access to the system.

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.0.1e or later
Fixed in 9.0.1e
Interim mitigation

Upgrade Brocade Fabric OS to version 9.0.1e, 9.1.0, or later to remediate the unsafe string function vulnerabilities. Alternatively, limit local authenticated access to trusted personnel only.

Recommended fix High confidence

9.0.1e or later (9.1.0 also contains fix)

  1. Verify current Fabric OS version using 'version' command
  2. Review Brocade Fabric OS upgrade guide for backup and upgrade procedures
  3. Ensure configuration backup is created before upgrade
  4. Download Fabric OS v9.0.1e or v9.1.0 (or later) from Broadcom support portal
  5. Follow standard Fabric OS firmware upgrade procedure using 'firmwareDownload' command
  6. Verify upgrade completion and new version using 'version' command
  7. Confirm vulnerability is resolved by verifying running version is >= 9.0.1e

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

Fix this in Fabric Operating System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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