CVE-2022-33182
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 privilege escalation vulnerability in Brocade Fabric OS CLI before Brocade Fabric OS v9.1.0, 9.0.1e, 8.2.3c, 8.2.0cbn5, could allow a local authenticated user to escalate its privilege to root using switch commands “supportlink”, “firmwaredownload”, “portcfgupload, license, and “fosexec”.
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 local privilege escalation vulnerability in Brocade Fabric OS CLI allows authenticated users to gain root privileges by abusing specific privileged commands (supportlink, firmwaredownload, portcfgupload, license, and fosexec). The vulnerability affects versions prior to v9.1.0, 9.0.1e, 8.2.3c, and 8.2.0cbn5.
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.0.0, < 8.2.3c>= 9.0.0, < 9.0.1eCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Fabric OS versionAccess the Fabric OS CLI and run the appropriate command to display the system version (such as 'version' or a similar version-displaying command). Record the exact version number shown.Affected if The installed version is 8.0.0 or higher but lower than 8.2.3c, or 9.0.0 or higher but lower than 9.0.1e
-
Confirm user access to privileged commandsQuery the system to determine if your user account has permission to execute the following privileged commands: supportlink, firmwaredownload, portcfgupload, license, and fosexec. This may be visible in role definitions, permission lists, or by attempting to access help for these commands.Affected if Your user account has access to one or more of these five privileged commands (supportlink, firmwaredownload, portcfgupload, license, or fosexec)
-
Verify user role and privilege levelCheck the current user session role or privilege level using CLI commands that display user permissions or role assignments.Affected if Your account holds any administrative, root, or elevated privileges within the Fabric OS CLI
You are affected if the Fabric OS version is within the vulnerable ranges (8.0.0 to below 8.2.3c, or 9.0.0 to below 9.0.1e) AND your user account has access to the vulnerable privileged commands.
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 · scoped8.2.3c9.0.1e
Upgrade Brocade Fabric OS to version 9.1.0 or later (or the appropriate patched version for your branch: 9.0.1e, 8.2.3c, or 8.2.0cbn5). Restrict CLI access to trusted personnel and follow least-privilege principles until patching is complete.
Fabric OS 9.1.0 or later (or 8.2.3c/8.2.0cbn5 for respective 8.x branches)
- 1. Identify the current Fabric OS version by running 'firmwareShow' or 'version' command in the CLI
- 2. For Fabric OS 8.x versions (>=8.0.0, <8.2.3c): Plan upgrade to version 8.2.3c or later
- 3. For Fabric OS 9.0.x versions (>=9.0.0, <9.0.1e): Plan upgrade to version 9.0.1e or later
- 4. For all versions: Plan upgrade to version 9.1.0 or later for the most complete fix
- 5. Schedule a maintenance window as firmware upgrades require switch downtime
- 6. Backup current configuration using 'configupload' command
- 7. Download the firmware from Broadcom/NetApp support portal
- 8. Run 'firmwaredownload' command to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.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,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33182 — 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-33182 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