dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29968

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 2.3.0a or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Brocade SANnav instances are configured in disaster recovery mode. SQL Table names, column names, and SQL queries are collected in DR standby Supportsave. This could allow authenticated users to access the database structure and its contents.

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

In Brocade SANnav versions before v2.3.1 and v2.3.0a, when configured in disaster recovery mode, the DR standby Supportsave collection process inadvertently includes SQL database schema information (table names, column names, and query structures). This allows authenticated users to access the underlying database structure and potentially its contents.

MitigationUpgrade Brocade SANnav to v2.3.1 or v2.3.0a. If immediate patching is not possible, restrict access to DR standby Supportsave files and review user access controls to minimize exposure.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Identify if Brocade SANnav is installed
    Locate the SANnav installation directory or check for the SANnav service/process running on the system. Common locations include /opt/brocade or the installation path used during initial setup.
    Affected if Brocade SANnav software is found running on the system
  2. Determine the installed SANnav version
    Check the SANnav version using the management interface, CLI command (such as 'sannav --version' or similar), or by examining version files in the installation directory.
    Affected if The installed version is earlier than v2.3.1 or v2.3.0a (versions < 2.3.0a)
  3. Verify if disaster recovery mode is configured
    Access the SANnav management interface or configuration settings to check whether the system is configured in disaster recovery (DR) mode, specifically looking at the DR standby configuration.
    Affected if Disaster recovery mode is enabled and the system is operating as a DR standby node
  4. Inspect Supportsave files for SQL schema exposure
    Locate and examine Supportsave collection files on the DR standby system. Search within these files for SQL table names, column names, CREATE TABLE statements, or query structures that reveal the underlying database schema.
    Affected if SQL database schema information (table names, column names, or query structures) is present in the Supportsave files

You are affected if SANnav is installed in disaster recovery mode and the version is earlier than v2.3.1 or v2.3.0a, with SQL schema data present in the DR standby Supportsave files.

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 Brocade SANnav to v2.3.1 or v2.3.0a. If immediate patching is not possible, restrict access to DR standby Supportsave files and review user access controls to minimize exposure.

Recommended fix Moderate confidence

SANnav v2.3.1 or later

  1. 1. Review the current Brocade SANnav version by navigating to the SANnav About page in the web interface
  2. 2. Confirm the SANnav instance is configured in disaster recovery (DR) mode, as this vulnerability only affects DR standby configurations
  3. 3. Download SANnav version 2.3.1 or later from the Broadcom Support Portal (support.broadcom.com)
  4. 4. Plan the upgrade during a maintenance window as recommended by Broadcom upgrade procedures
  5. 5. Follow the standard SANnav upgrade documentation to apply version 2.3.1 or later
  6. 6. After upgrade, verify the DR standby Supportsave no longer contains SQL table names, column names, or SQL queries in the output
  7. 7. Confirm normal SANnav operation and DR functionality post-upgrade
Caveat Standard SANnav upgrade procedures apply - review release notes for any configuration or compatibility considerations

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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