CVE-2024-4159
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 v2.3.0a lacks protection mechanisms on port 2377/TCP and 7946/TCP, which could allow an unauthenticated attacker to sniff the SANnav Docker information.
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.3.0a expose Docker Swarm management ports 2377/TCP and 7946/TCP without authentication or encryption protections. An unauthenticated remote attacker can connect to these ports and sniff Docker container orchestration information, potentially revealing sensitive infrastructure details about the SAN management environment.
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.3.0aCVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 and versionLocate the Brocade SANnav installation and determine its version number. This may be found in the product UI, in an installation directory, or via a version command specific to the SANnav application.Affected if The installed version is lower than 2.3.0a (e.g., 2.2.x, 2.1.x, or earlier)
-
Check if port 2377/TCP is exposedScan the SANnav server or appliance from an untrusted network perspective using a port scanner (such as nmap) targeting port 2377. Alternatively, run 'netstat -an | grep 2377' or 'ss -tlnp | grep 2377' on the SANnav host to see if the port is listening.Affected if Port 2377/TCP is open and accepting connections from an untrusted network
-
Check if port 7946/TCP is exposedScan the SANnav server or appliance targeting port 7946 using a port scanner, or run 'netstat -an | grep 7946' or 'ss -tlnp | grep 7946' on the SANnav host.Affected if Port 7946/TCP is open and accessible from an untrusted network
-
Verify Docker Swarm service statusIf you have command-line access to the SANnav server, check if Docker Swarm is initialized or running. This may involve running 'docker info' or checking Docker service configurations.Affected if Docker Swarm is active and the exposed ports are being used for container orchestration communication
A system is affected if it runs Brocade SANnav with a version below 2.3.0a and has ports 2377/TCP or 7946/TCP exposed to untrusted networks, allowing unauthenticated access to Docker Swarm orchestration data.
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.3.0a
Upgrade Brocade SANnav to version 2.3.0a or later. Additionally, implement network segmentation and firewall rules to restrict access to ports 2377 and 7946 to only trusted management networks.
SANnav v2.3.0a
- Obtain the SANnav version 2.3.0a or later from the Broadcom support portal at support.broadcom.com
- Review the SANnav upgrade documentation and release notes for version 2.3.0a
- Back up the current SANnav configuration and database before initiating the upgrade
- Deploy the SANnav 2.3.0a upgrade package following the documented upgrade procedure
- Verify that the upgrade completed successfully and that ports 2377/TCP and 7946/TCP are now properly protected
- Confirm that the SANnav services are running correctly after the upgrade
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-2024-4159 — 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-2024-4159 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