dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-4173

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-25
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in Brocade SANnav exposes Kafka in the wan interface. The vulnerability could allow an unauthenticated attacker to perform various attacks, including DOS against the Brocade SANnav.

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 · moderate confidence

Brocade SANnav has a critical exposure where the Kafka distributed streaming platform is bound to or accessible through the WAN interface. Kafka, which handles message queuing and can consume significant system resources, is thus exposed to unauthenticated network attackers who can exploit this for denial of service or other attacks.

MitigationRestrict network access to Kafka ports on the WAN interface through firewall rules or network segmentation to prevent external access; apply vendor patches when available.

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
Brocade SannavApplication
Affected:< 2.2.0

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check SANnav version
    Access SANnav admin UI and navigate to 'About' or 'System Information' page to view the installed version number, or run: docker ps | grep sannav to find the container and check its version label
    Affected if Version is below 2.2.0
  2. Identify Kafka listening ports
    Run 'netstat -tlnp' or 'ss -tlnp' on the SANnav server to list all listening TCP ports. Look for default Kafka ports 9092 or 9093 in the output
    Affected if Kafka ports (9092/9093) are listening on any interface
  3. Verify Kafka binding address
    Examine Kafka server.properties configuration file typically located in /opt/brocade/sannav/kafka/config/server.properties and check the 'listeners' or 'advertised.listeners' parameter. If set to 0.0.0.0 or WAN IP, it is exposed
    Affected if Kafka listeners are bound to 0.0.0.0 or an IP accessible from WAN
  4. Check WAN interface exposure
    Run 'ip addr show' or 'ip route' to identify the WAN-facing network interface (typically the interface with public/external IP). Then check which addresses Kafka is listening on: 'netstat -tlnp | grep 9092'
    Affected if Kafka port is listening on the same IP/subnet as the WAN interface
  5. Test external Kafka port accessibility
    From an external network (or using an online port scanner from outside your network), attempt to connect to the public IP on ports 9092/9093. If connection succeeds, Kafka is externally accessible
    Affected if TCP connection to Kafka ports succeeds from external network

User is affected if SANnav version is below 2.2.0 AND Kafka ports (9092/9093) are listening on an interface reachable from the WAN/untrusted network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Restrict network access to Kafka ports on the WAN interface through firewall rules or network segmentation to prevent external access; apply vendor patches when available.

Recommended fix Moderate confidence

2.2.0

  1. Upgrade Brocade SANnav to version 2.2.0 or later to remediate the Kafka exposure vulnerability
  2. Before upgrading, back up the current SANnav configuration and database
  3. Review the SANnav 2.2.0 release notes for any specific upgrade prerequisites or migration requirements
  4. Execute the upgrade following the standard SANnav upgrade procedure (refer to Broadcom documentation for your specific deployment type)
  5. After upgrade, verify that Kafka is no longer exposed on the WAN interface by reviewing network configurations
  6. Confirm SANnav services are running normally post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4173 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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