CVE-2022-43934
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 · uneditedBrocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095.
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 prior to 2.2.2 support weak key exchange algorithms in SSH/TLS implementations on ports 24, 6514, 18023, 19094, and 19095. These weak algorithms could allow an attacker with man-in-the-middle capabilities to influence or break the key exchange, potentially compromising session confidentiality and integrity.
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.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.
-
Identify SANnav installation versionAccess the SANnav management interface or check the system where SANnav is installed to find the installed version number. This is typically visible in the web UI footer, about page, or via CLI commands if available.Affected if The installed version is any release prior to 2.2.2 (for example, 2.2.1, 2.2.0, 2.1.x, 2.0.x, or 1.x).
-
Identify exposed management portsScan the SANnav host or management network for open ports 24, 6514, 18023, 19094, and 19095 using a network port scanner or by reviewing firewall rules and listening services.Affected if Any of the ports 24, 6514, 18023, 19094, or 19095 are accessible from network segments where an attacker could perform man-in-the-middle attacks.
-
Verify SSH/TLS key exchange configurationIf you have CLI or API access to SANnav, review the SSH and TLS configurations on the affected ports. Use tools like nmap with the ssl-enum-ciphers script or ssh-audit to probe the exposed ports and identify supported key exchange algorithms.Affected if The SSH or TLS services on ports 24, 6514, 18023, 19094, or 19095 advertise or accept weak key exchange algorithms such as diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, or other known-weak algorithms.
You are affected if SANnav version is below 2.2.2 AND any of the ports 24, 6514, 18023, 19094, or 19095 are exposed with weak key exchange algorithms enabled.
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.2
Upgrade Brocade SANnav to version 2.2.2 or later, which removes support for weak key exchange algorithms. If immediate upgrade is not possible, restrict network access to the affected ports and monitor for anomalous connection attempts.
Brocade SANnav 2.2.2
- Upgrade Brocade SANnav to version 2.2.2 or later
- After upgrading, verify that the weak key exchange algorithms are no longer supported on the affected ports (24, 6514, 18023, 19094, and 19095)
- Confirm the upgrade was successful and review SANnav documentation for any post-upgrade configuration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43934 — 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-43934 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