CVE-2024-29950
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 · uneditedThe class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signature scheme, which has a SHA-1 hash. The vulnerability could allow a remote, unauthenticated attacker to perform a man-in-the-middle attack.
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's FileTransfer class uses the ssh-rsa signature scheme which employs the cryptographically weak SHA-1 hash algorithm. This allows a remote, unauthenticated attacker to potentially perform a man-in-the-middle attack by exploiting known weaknesses in SHA-1 for signature forgery.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 installationLocate the Brocade SANnav installation and access its web management interface or check system information for the SANnav version numberAffected if The system is running Broadcom Brocade SANnav and the version cannot be determined or is visible in the interface
-
Determine installed versionCheck the SANnav management console or system files for the exact version number (typically found in About or System Info section of the web UI, or via CLI commands like 'sannav --version' if available)Affected if The installed version is lower than 2.3.0a (e.g., 2.2.x, 2.1.x, etc.)
-
Verify FileTransfer feature is in useCheck if FileTransfer functionality is enabled or used within SANnav - look for file transfer configuration, backup/restore features, or logs showing file transfer operationsAffected if FileTransfer class functionality is active and the version is vulnerable (< 2.3.0a)
-
Check network exposureReview network access controls and determine if the SANnav management interface is exposed to untrusted networksAffected if SANnav management interface is accessible from network segments that include untrusted or external systems
A system is affected if it runs Broadcom Brocade SANnav version lower than 2.3.0a and has the FileTransfer feature accessible from the network.
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.1 or v2.3.0a to replace the vulnerable ssh-rsa/SHA-1 implementation with a modern signature scheme.
SANnav v2.3.1 or later
- 1. Log into the Brocade SANnav management interface
- 2. Navigate to the Administration or System Settings section
- 3. Check the current SANnav version under About or Version information
- 4. Download the SANnav v2.3.1 or later release from the Broadcom support portal (support.broadcom.com)
- 5. Review upgrade prerequisites and backup procedures in the SANnav installation guide
- 6. Execute the upgrade following the documented upgrade procedure for your deployment type (single server or cluster)
- 7. After upgrade, verify the new version is running under About/System Information
- 8. Confirm the FileTransfer functionality is working normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29950 — 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-29950 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