Safeguard
Vulnerability Analysis•

CVE-2022-43934: Medium Weak Key Exchange in Brocade SANnav

CVE-2022-43934 is a medium (6.5) weak key exchange issue on five ports in Brocade SANnav before 2.2.2. Upgrade to 2.2.2 or later and check the advisory.

Safeguard Security Team
3 min read

CVE-2022-43934 is a medium severity (CVSS 6.5) weakness in Brocade SANnav before version 2.2.2, which supports weak key exchange algorithms on ports 24, 6514, 18023, 19094 and 19095. Upgrade to 2.2.2 or later, and read the Broadcom advisory for the full detail.

What's affected

The record says Brocade SANnav before 2.2.2 supports key exchange algorithms that are considered weak on ports 24, 6514, 18023, 19094 and 19095. The fixed version implied by the record is 2.2.2.

I could not read the Broadcom advisory, because its page requires JavaScript and returned a challenge page when fetched. So this post relies on the record alone, and you should read the advisory itself, which Broadcom lists as security advisory 21220 in the record's reference, before you plan the change.

The record scores it 6.5 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. The class is CWE-327 (Use of a Broken or Risky Cryptographic Algorithm).

How to check if you're exposed

Check the SANnav version in the management interface. Anything before 2.2.2 is in the affected range.

You can also test which key exchange algorithms a listening port offers. For SSH style services on a port you own, a scan with nmap's ssh2-enum-algos script lists the offered key exchange methods, and for TLS services the ssl-enum-ciphers script shows ciphers. Run these only against your own systems:

nmap -p 24 --script ssh2-enum-algos YOUR-SANNAV-HOST
nmap -p 6514 --script ssl-enum-ciphers YOUR-SANNAV-HOST

I do not know from the record which protocol each of the five ports speaks, so use the advisory to decide which test fits which port.

What to do now

  1. Find your SANnav instances and their versions.
  2. Upgrade to 2.2.2 or later.
  3. Read the Broadcom advisory to learn which algorithms are considered weak and whether any configuration change is also required.
  4. Restrict network access to the five listed ports to management networks.
  5. Re-scan the ports after the upgrade to confirm the weak algorithms are gone.

Why it matters

Key exchange is how two systems agree on the secret that protects a session. If a service still offers old, weak methods, an attacker who can sit in the network path may force a downgrade or break the exchange, and then read or tamper with the traffic. The record scores the impact as high on confidentiality only, with a low privilege requirement.

A storage network management product matters more than its score suggests. SANnav manages storage fabric devices, so anything its sessions carry, such as credentials and configuration, is valuable. The record's KEV flag is false, and I found no report of exploitation. Because I could not read the advisory, I do not state which algorithms are involved.

Quick check

Why does the post rely on the record only?

Broadcom's advisory page returned a JavaScript challenge when fetched, so I could not read it. Read it before acting.

Which ports are involved?

The record lists 24, 6514, 18023, 19094 and 19095.

Sources

Reference from the NVD record, not retrievable when this was reviewed: Broadcom security advisory 21220.

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.