dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29957

HIGH · 7.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 2.3.0a or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
When Brocade SANnav before v2.3.1 and v2.3.0a servers are configured in Disaster Recovery mode, the encryption key is stored in the DR log files. This could provide attackers with an additional, less-protected path to acquiring the encryption key.

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

When Brocade SANnav is configured in Disaster Recovery mode, the encryption key is stored in plain text in DR log files. This creates an exposed path to the encryption key that lacks the protection mechanisms applied to the primary key storage, potentially allowing authenticated attackers with log file access to obtain the encryption key.

MitigationUpgrade to SANnav v2.3.1 or v2.3.0a or later versions to remediate this vulnerability. As an interim measure, restrict access to DR log files and implement additional monitoring on these files.

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

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

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

  1. Check SANnav version
    Use the SANnav admin interface or command line to determine the installed version of Brocade SANnav. Consult product documentation for the exact command or UI location to retrieve the version number.
    Affected if The installed version is any release prior to 2.3.0a (for example, 2.3.0, 2.2.x, 2.1.x, or earlier).
  2. Verify Disaster Recovery mode is enabled
    Access the SANnav administrative console and confirm whether the instance is configured in Disaster Recovery mode. Check the DR configuration settings or status page to determine if DR mode is active.
    Affected if Disaster Recovery mode is enabled and the SANnav version is below 2.3.0a.
  3. Locate DR log files
    Identify and access the log files associated with Disaster Recovery functionality in the SANnav installation. These are typically found in the log directory structure under the DR-related logging paths.
    Affected if DR log files exist on the system and are accessible to authenticated users.
  4. Inspect DR log files for plain text encryption keys
    Search within the DR log files for patterns that resemble encryption keys stored in plain text. Use text search tools to examine the contents of these log files for key material.
    Affected if The encryption key is present in plain text within the DR log files.

A system is affected if it runs Brocade SANnav version below 2.3.0a with Disaster Recovery mode enabled, and the DR log files contain the encryption key in plain text format.

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 SANnav v2.3.1 or v2.3.0a or later versions to remediate this vulnerability. As an interim measure, restrict access to DR log files and implement additional monitoring on these files.

Recommended fix High confidence

SANnav v2.3.1 or later

  1. 1. Log in to the Brocade SANnav management interface with administrator credentials.
  2. 2. Navigate to the SANnav version and system settings to check the current installed version.
  3. 3. Confirm the current version is below v2.3.1 (or v2.3.0a).
  4. 4. Download the SANnav v2.3.1 or later release from the Broadcom support portal at support.broadcom.com.
  5. 5. Review the SANnav upgrade guide and release notes for upgrade prerequisites and procedures.
  6. 6. Perform a complete backup of the SANnav configuration and data, including any encryption keys used for Disaster Recovery.
  7. 7. Follow the documented upgrade procedure to upgrade SANnav to v2.3.1 or later.
  8. 8. After upgrade, verify that SANnav is functioning correctly and the Disaster Recovery feature is operational.
Caveat Review SANnav v2.3.1 release notes for any compatibility changes or configuration adjustments required; ensure backup before upgrading

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

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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