dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29964

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
Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files. An unprivileged attacker who gains access to the server can read sensitive information from these files.

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

Brocade SANnav versions before v2.3.0a set overly permissive file permissions (likely 644 or world-readable) on sensitive files including docker-related configuration files. An unprivileged local user or attacker who gains any server access can read these files to obtain sensitive information such as credentials, API keys, or configuration secrets.

MitigationUpgrade to Brocade SANnav v2.3.0a or later which corrects file permissions. If immediate upgrade is not possible, audit and restrict permissions on docker files and other sensitive configuration files to owner-only (600 or 640).

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 SANnav installation and version
    Locate the SANnav installation directory and check the version file or use the SANnav management interface to determine the installed version. Common locations include /opt/sannav or the application root directory.
    Affected if The installed version is anything before 2.3.0a (e.g., 2.2.0, 2.1.0, etc.)
  2. Locate docker configuration files
    Search for docker-related configuration files in the SANnav installation directory, typically under the config or data subdirectories. Look for files such as docker-compose.yml, docker.env, or similar configuration files that may contain credentials or API keys.
    Affected if Docker configuration files exist in the SANnav installation directory and contain sensitive information such as passwords, API keys, or secrets in plain text
  3. Check file permissions on sensitive configuration files
    Use 'ls -la' or 'stat' commands to examine the permissions on docker configuration files and other sensitive files (e.g., configuration files, credential files, environment files). Look for permissions like 644 (rw-r--r--) or 666 (rw-rw-rw-) which allow world read access.
    Affected if Sensitive files have permissions that allow read access by any user on the system (e.g., 644, 655, 666, or other non-600/640 permissions)
  4. Verify world-readable status
    As a non-privileged user test if you can read the sensitive configuration files using 'cat <filename>' or 'readlink -f <filename>' without elevated privileges.
    Affected if A non-privileged user account on the same system can successfully read docker configuration or other sensitive files containing credentials

You are affected if SANnav version is before 2.3.0a AND sensitive configuration files (particularly docker-related) have overly permissive file permissions allowing non-privileged users to read them.

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.0a or later which corrects file permissions. If immediate upgrade is not possible, audit and restrict permissions on docker files and other sensitive configuration files to owner-only (600 or 640).

Recommended fix High confidence

2.3.0a

  1. Backup the current SANnav installation and configuration
  2. Download SANnav version 2.3.0a or later from support.broadcom.com
  3. Stop the current SANnav services
  4. Install SANnav version 2.3.0a using the standard upgrade procedure
  5. Start the SANnav services
  6. Verify the upgrade was successful by checking the SANnav version
  7. Confirm that file permissions on sensitive files are now correctly restricted

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-29964 — 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-29964 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