dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29962

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 2.3.0a or later.
See remediation →
57/100
Remediation priority · Elevated
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 OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes files world-readable. This could allow a local user without the required privileges to access sensitive information or a Java binary.

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

Brocade SANnav OVA versions before v2.3.1 and v2.3.0a contain insecure file permission settings that make files world-readable. This allows any local user on the virtual appliance to access sensitive information or Java binaries that should be restricted to privileged users only.

MitigationUpgrade to Brocade SANnav OVA v2.3.1 or later which corrects the file permission settings to restrict access appropriately.

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

CVSS:3.1/AV:L/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. Confirm SANnav OVA installation
    Locate the SANnav installation directory or check system for Brocade SANnav OVA presence. Common locations include /opt/brocade/sannav or the directory where the OVA was deployed.
    Affected if SANnav OVA is installed on the system
  2. Identify installed SANnav version
    Run the SANnav version command or check the version file in the installation directory. Use: sannav --version or check version info in the application directory.
    Affected if The installed version is earlier than 2.3.0a (any version < 2.3.0a)
  3. Verify file permissions on sensitive directories
    List file permissions in SANnav directories using: ls -la /opt/brocade/sannav/ or the relevant installation path. Look for directories or files with permissions showing 'r--r--r--' (world-readable).
    Affected if Sensitive files or Java binary directories show world-readable permissions (mode 644 or 755 with 'other' read bit set)
  4. Check for world-readable Java binaries
    Examine Java binaries and library files in the SANnav installation for world-readable permissions. Use: find /opt/brocade/sannav -name '*.jar' -o -name 'java' -ls | grep -E 'r--r--r--|rwxrwxrwx'
    Affected if Java binaries or sensitive JAR files are world-readable

The environment is affected if SANnav OVA version is earlier than 2.3.0a AND sensitive files in the SANnav installation directory have world-readable permissions accessible to any local user.

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 OVA v2.3.1 or later which corrects the file permission settings to restrict access appropriately.

Recommended fix Moderate confidence

SANnav v2.3.1 or later

  1. 1. Verify the current Brocade SANnav OVA version by logging into the SANnav management interface
  2. 2. Access the Broadcom support portal at support.broadcom.com and navigate to the SANnav downloads section
  3. 3. Download the fixed version (v2.3.1 or later) of the SANnav OVA
  4. 4. Before upgrading, perform a full backup of the current SANnav configuration and data
  5. 5. Deploy the upgraded SANnav OVA following the standard upgrade procedure documented in the SANnav Installation and Upgrade Guide
  6. 6. After upgrade, verify that file permissions are no longer world-readable by checking that sensitive files are properly protected
Caveat Standard upgrade risks apply - ensure backup before proceeding; review upgrade guide for any migration requirements

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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