CVE-2022-33186
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 software v9.1.1, v9.0.1e, v8.2.3c, v7.4.2j, and earlier versions could allow a remote unauthenticated attacker to execute on a Brocade Fabric OS switch commands capable of modifying zoning, disabling the switch, disabling ports, and modifying the switch IP address.
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 confidenceA pre-authentication vulnerability in Brocade Fabric OS allows remote unauthenticated attackers to execute arbitrary privileged commands, enabling modification of zoning configurations, disabling switches/ports, and altering switch IP settings. The flaw affects versions 9.1.1, 9.0.1e, 8.2.3c, 7.4.2j and earlier.
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.2j= 8.2.3c= 9.0.1e= 9.1.1CVSS 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 the Fabric OS versionLog into the Brocade switch CLI and run the 'version' command or 'firmwareShow' to display the installed Fabric OS versionAffected if The displayed version matches 9.1.1, 9.0.1e, 8.2.3c, 7.4.2j, or any version earlier than these releases (for example, 7.4.x versions earlier than 7.4.2j)
-
Confirm the exact firmware buildRun 'firmwareShow' to see the detailed firmware build string including any letter suffixes (such as 'c' in 8.2.3c or 'e' in 9.0.1e)Affected if The build string matches one of the affected versions: 9.1.1, 9.0.1e, 8.2.3c, or 7.4.2j exactly
-
Check if this is a standalone or management-connected switchRun 'ipaddrshow' or 'licenseshow' to confirm the switch has an active management IP address and is reachable over the networkAffected if The switch has an active management interface and is network-accessible; since this is a pre-authentication vulnerability, remote attackers can exploit it if the management interface is exposed
You are affected if your switch runs Fabric OS version 9.1.1, 9.0.1e, 8.2.3c, 7.4.2j, or any earlier version and has its management interface accessible from untrusted networks.
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 the vendor-released patched version of Brocade Fabric OS for all affected installations; if immediate patching is not possible, restrict network access to management interfaces using firewalls or ACLs.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33186 — 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-2022-33186 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