dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29965

MEDIUM · 5.9 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 2.3.0a or later.
See remediation →
59/100
Remediation priority · Elevated

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
In Brocade SANnav before v2.3.1, and v2.3.0a, it is possible to back up the appliance from the web interface or the command line interface ("SSH"). The resulting backups are world-readable. A local attacker can recover backup files, restore them to a new malicious appliance, and retrieve the passwords of all the switches.

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 confidence

In Brocade SANnav before v2.3.1, backup files created via the web interface or CLI are stored with world-readable permissions, allowing any local user to read sensitive backup data containing switch credentials.

MitigationUpgrade to Brocade SANnav v2.3.1 or later which corrects the backup file permissions. Until then, restrict local system access and manually audit backup file permissions.

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.3.0a

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 checks

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

  1. Identify SANnav installation and version
    Locate the SANnav installation directory and determine the installed version (typically via web interface, CLI, or installation metadata)
    Affected if Installed version is lower than 2.3.0a
  2. Determine if backup functionality is used
    Check whether SANnav backup features have been used (via web interface or CLI) to create backup files
    Affected if Any backup files have been created using SANnav's backup feature
  3. Inspect backup file permissions
    Examine the file permissions on SANnav backup files (look for world-readable permissions, typically indicated by 'r--r--r--' or 'o+r' in permission strings)
    Affected if Backup files grant read access to all users (world-readable)
  4. Verify sensitive data exposure risk
    Confirm that backup files contain switch credentials or other sensitive configuration data that could be read by any local user
    Affected if Backup files are world-readable AND contain credentials or sensitive data

User is affected if running SANnav version lower than 2.3.0a AND backup files exist with world-readable permissions, allowing any local user to access sensitive switch credentials.

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.3.0a or later
Fixed in 2.3.0a
Interim mitigation

Upgrade to Brocade SANnav v2.3.1 or later which corrects the backup file permissions. Until then, restrict local system access and manually audit backup file permissions.

Recommended fix High confidence

SANnav v2.3.1 or later

  1. Navigate to the Broadcom Support Portal (support.broadcom.com) and download Brocade SANnav version 2.3.1 or later
  2. Review the official SANnav upgrade guide for your current version to ensure compatibility
  3. Schedule a maintenance window for the upgrade process
  4. Create a backup of the current SANnav installation before upgrading (note: this backup may still be vulnerable until the upgrade is complete)
  5. Upgrade SANnav to version 2.3.1 or later following the official upgrade procedure
  6. After the upgrade, verify that new backup files have restrictive permissions (not world-readable) by examining the backup file permissions
  7. Test the backup and restore functionality on a non-production system to confirm the fix works correctly
Caveat Review SANnav release notes for v2.3.1 to check for any configuration or feature changes that may require adjustments

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

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29965 — 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-29965 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