CVE-2022-28166
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 · uneditedIn Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Static Key Ciphers (ssl-static-key-ciphers) on ports 443 & 18082.
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 SANnav versions before 2.2.0.2 and 2.1.1.8 have a vulnerability where the TLS/SSL implementation supports static key ciphers on management ports 443 and 18082. Static key ciphers reuse the same cryptographic key across multiple sessions, eliminating forward secrecy and making encrypted communications vulnerable to cryptanalysis, replay attacks, or key recovery.
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.1.1.8>= 2.2.0.0, < 2.2.0.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify SANnav installationCheck for SANnav processes or installation directories on the system. Look for SANnav-related services running.Affected if Brocade SANnav software is installed on the system
-
Check installed SANnav versionLocate and read the SANnav version file or use SANnav version lookup methods to determine the exact version number.Affected if Version is less than 2.1.1.8 OR version is 2.2.0.0 or 2.2.0.1 (any version >= 2.2.0.0 but < 2.2.0.2)
-
Confirm management ports are accessibleVerify that management ports 443 and/or 18082 are listening and accessible using network scanning tools (netstat, nmap, or similar).Affected if Ports 443 or 18082 are open and accepting connections
-
Inspect TLS cipher configuration on management portsUse SSL/TLS testing tools (such as openssl s_client, nmap ssl-enum-ciphers, or SSL Labs test) to query the supported cipher suites on ports 443 and 18082.Affected if Static key ciphers (ciphers that do not use ephemeral/key exchange) are among the supported cipher suites
-
Verify forward secrecy is absentAnalyze the cipher suite list from the management ports to determine if ephemeral key exchange ciphers (DHE, ECDHE) are missing or unavailable.Affected if No forward secrecy ciphers (DHE, ECDHE) are available, only static key ciphers are enabled
A system is affected if it runs any version of Brocade SANnav below 2.1.1.8 or between 2.2.0.0 and 2.2.0.1 inclusive, AND has management ports 443 or 18082 configured with static key ciphers that lack forward secrecy.
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.1.1.82.2.0.2
Upgrade Brocade SANnav to version SANN2.2.0.2 or 2.1.1.8 or later, or reconfigure the SSL/TLS settings to disable static key ciphers and enable only cipher suites that provide forward secrecy.
SANnav 2.2.0.2 or later (2.2.x line); alternatively SANnav 2.1.1.8 or later (2.1.x line)
- Identify current SANnav version via web UI (Help > About) or CLI (show version)
- Review current configuration and document settings
- Backup current configuration and database per Brocade SANnav backup procedures
- Download the fixed version (2.1.1.8 or later for 2.1.x line, 2.2.0.2 or later for 2.2.x line) from Broadcom support portal
- Schedule maintenance window as upgrade requires service restart
- Stop SANnav services per official upgrade documentation
- Install the fixed version following Broadcom SANnav upgrade guide
- After upgrade, verify ports 443 and 18082 no longer accept static key ciphers using SSL/TLS scanning tools (e.g., openssl s_client, nmap with ssl-enum-ciphers)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28166 — 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-28166 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