CVE-2022-28165
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 the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an authenticated, remote attacker to access resources that they should not be able to access and perform actions that they should not be able to perform. The vulnerability exists because restrictions are not performed on Server side to ensure the user has required permission before processing requests.
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 confidenceThis is a server-side authorization bypass in Brocade SANNav's RBAC implementation. The vulnerability allows authenticated users to access resources and perform actions outside their assigned permissions because the server does not validate user permissions before processing requests. This is a classic broken access control vulnerability where trust is placed client-side without server-side verification.
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< 2.2.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Confirm SANNav installationIdentify if Brocade SANNav or Broadcom SANNav is installed in your environment. Check for SANNav management interfaces, typically accessible on ports 8443 or 443.Affected if The system is running Brocade SANNav or Broadcom SANNav
-
Determine installed versionAccess the SANNav admin web interface and navigate to the About or System Information section to retrieve the version number. Alternatively, check version files or the management console if available.Affected if The installed version is prior to 2.2.0
-
Verify RBAC is configuredLog into SANNav administration and navigate to User Management or Access Control settings. Confirm Role-Based Access Control is enabled and multiple user roles are defined.Affected if RBAC is enabled with defined user roles and permissions
-
Audit user role assignmentsReview the list of users and their assigned roles in the SANNav management interface. Identify users with limited or restricted permissions.Affected if Users with restricted roles exist in the system
If SANNav version is below 2.2.0 and RBAC is configured with multiple user roles, the environment is affected by this authorization bypass vulnerability.
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 · scoped2.2.0
Upgrade Brocade SANNav to version 2.2.0 or later to obtain the vendor patch that adds proper server-side permission validation. Restrict network access to SANNav management interfaces until the patch can be applied.
SANNav 2.2.0 or later
- 1. Backup the current SANNav configuration and database according to Broadcom backup procedures
- 2. Download SANNav version 2.2.0 or later from the Broadcom support portal at www.broadcom.com
- 3. Review the SANNav upgrade guide for version 2.2.0 to ensure prerequisites are met (disk space, memory,停止了 services)
- 4. Stop all SANNav services before beginning the upgrade
- 5. Run the SANNav upgrade installer as documented in the upgrade guide
- 6. Monitor the upgrade process for any errors
- 7. After upgrade completes, start SANNav services
- 8. Verify the upgrade was successful by checking the SANNav version in the administration console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.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 $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28165 — 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-28165 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