dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29952

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-17
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
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to print the Auth, Priv, and SSL key store passwords in unencrypted logs by manipulating command variables.

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.1 and v2.3.0a contain an information disclosure vulnerability where authenticated users can manipulate command variables to cause Auth, Priv, and SSL key store passwords to be written to unencrypted application logs, exposing sensitive credential data.

MitigationUpgrade Brocade SANnav to v2.3.1 or v2.3.0a to patch the vulnerability. Review existing logs for exposure of sensitive passwords and rotate any compromised credentials as a precautionary measure.

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. Determine SANnav installed version
    Access the SANnav administration interface and navigate to the About or System Information section to view the current software version. Alternatively, check the installation directory for version metadata files or use the SANnav CLI if available.
    Affected if The installed version is lower than 2.3.0a (for example, 2.3.0, 2.2.x, or earlier releases).
  2. Identify SANnav log file locations
    Locate the SANnav application log directories, typically found under the SANnav installation path in logs or tomcat directories. Common paths include <install_dir>/logs/ or /opt/sannav/logs/.
    Affected if Log directories exist and are accessible to the application user account.
  3. Search logs for exposed password patterns
    Use grep or similar text search tools to scan log files for patterns indicating password exposure. Look for strings like 'password=', 'PASSWORD', 'keyStorePassword', 'privPassword', 'authPassword', or credential values appearing in plain text within log entries.
    Affected if Log files contain any plain-text instances of Auth, Priv, or SSL key store passwords that should not be present.
  4. Verify log file permissions
    Check file permissions on log directories and files to determine if unauthorized users could read sensitive log content. Use ls -la commands on the identified log paths.
    Affected if Log files have overly permissive read access (world-readable) or are accessible to non-admin users.

A system is affected if it runs SANnav version lower than 2.3.0a and contains log files with exposed credential data from Auth, Priv, or SSL key store passwords.

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 to patch the vulnerability. Review existing logs for exposure of sensitive passwords and rotate any compromised credentials as a precautionary measure.

Recommended fix High confidence

SANnav v2.3.1 or later

  1. 1. Log in to the Brocade SANnav management interface
  2. 2. Navigate to the Administration or Settings section
  3. 3. Locate the SANnav version information
  4. 4. Download the latest SANnav version (v2.3.1 or later) from the Broadcom support portal at support.broadcom.com
  5. 5. Follow the standard SANnav upgrade procedure documented in the SANnav Installation and Migration Guide
  6. 6. After upgrade, verify that the Auth, Priv, and SSL key store passwords are no longer being written to unencrypted logs
  7. 7. Review system logs to confirm the vulnerability has been remediated
Caveat Review SANnav release notes for any new feature requirements or configuration changes before upgrading; ensure backup of current configuration is performed

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