CVE-2024-10405
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 SANnav 2.3.1b enables weak TLS ciphers on ports 443 and 18082. In case of a successful exploit, an attacker can read Brocade SANnav data stream that includes monitored Brocade Fabric OS switches performance data, port status, zoning information, WWNs, IP Addresses, but no customer data, no personal data and no secrets or passwords, as it travels across the network.
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 before version 2.3.1b has weak TLS cipher suites enabled on ports 443 (web UI) and 18082 (REST API), allowing a man-in-the-middle attacker to potentially decrypt sensitive but non-personal operational data including switch performance metrics, port status, zoning configurations, WWNs, and IP addresses as they traverse the network.
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.1bCVSS 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 SANnav installation and determine the installed version number using the system's software inventory or version check mechanismAffected if The installed version is anything less than 2.3.1b (e.g., 2.3.0, 2.2.x, earlier releases)
-
Confirm exposed management portsVerify that ports 443 (web UI) and/or 18082 (REST API) are accessible on the SANnav hostAffected if Either port 443 or 18082 is exposed and accepting connections
-
Inspect TLS cipher configuration on port 443Connect to the SANnav web UI on port 443 and enumerate the supported TLS cipher suites, looking for weak or deprecated ciphers such as those with RSA key exchange, CBC mode ciphers, or export-grade ciphersAffected if Weak cipher suites are listed as supported or enabled on port 443
-
Inspect TLS cipher configuration on port 18082Connect to the SANnav REST API on port 18082 and enumerate the supported TLS cipher suites, looking for weak or deprecated ciphers such as those with RSA key exchange, CBC mode ciphers, or export-grade ciphersAffected if Weak cipher suites are listed as supported or enabled on port 18082
You are affected if SANnav version is below 2.3.1b AND weak TLS cipher suites are enabled on either port 443 or port 18082.
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.1b
Upgrade to SANnav version 2.3.1b or later, which disables weak TLS ciphers, and verify that only strong cipher suites are accepted on affected ports.
SANnav 2.3.1b or later
- Obtain SANnav version 2.3.1b or later from Broadcom support portal at support.broadcom.com
- Follow standard SANnav upgrade procedures to apply the update to your SANnav installation
- After upgrade, verify that ports 443 and 18082 are now using strong TLS 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-2024-10405 — 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-10405 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