dbcve.org
Brocade SannavApplication · Broadcom

CVE-2023-31423

MEDIUM · 5.5 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to 2.2.2a 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
Possible information exposure through log file vulnerability where sensitive fields are recorded in the configuration log without masking on Brocade SANnav before v2.3.0 and 2.2.2a. Notes: To access the logs, the local attacker must have access to an already collected Brocade SANnav "supportsave" outputs.

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 2.3.0 and 2.2.2a write sensitive configuration fields to log files without masking or redacting them. An attacker with local access to 'supportsave' output files (collected for support diagnostics) can read these unmasked sensitive fields.

MitigationUpgrade Brocade SANnav to version 2.3.0 or 2.2.2a or later, which implements proper masking of sensitive fields in configuration logs.

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.2.2a

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. Verify Brocade SANnav installation
    Identify if Brocade SANnav is deployed in your environment. This is typically installed on a management server for SAN fabric administration.
    Affected if SANnav is not installed in your environment, this CVE does not apply.
  2. Determine installed SANnav version
    Locate and check the SANnav version installed in your environment. Consult your system documentation for the command or interface to retrieve the version number.
    Affected if The installed version is before 2.2.2a or before 2.3.0, placing it within the vulnerable version range.
  3. Locate supportsave output files
    Search for supportsave output files or directories that contain diagnostic data collected from your SANnav installation. These are typically created during support diagnostic procedures.
    Affected if No supportsave output files exist, the vulnerability cannot be exploited through this attack vector.
  4. Inspect log files for unmasked sensitive fields
    Examine configuration log files within the supportsave output for sensitive fields such as passwords, keys, secrets, or credentials that appear in plain text rather than masked or redacted.
    Affected if Log files contain unmasked sensitive configuration fields, your environment is affected by this vulnerability.

Your environment is affected if Brocade SANnav version is before 2.2.2a (or before 2.3.0) AND supportsave output log files contain unmasked sensitive configuration fields.

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.2.2a or later
Fixed in 2.2.2a
Interim mitigation

Upgrade Brocade SANnav to version 2.3.0 or 2.2.2a or later, which implements proper masking of sensitive fields in configuration logs.

Recommended fix Moderate confidence

SANnav v2.2.2a or v2.3.0 (or later)

  1. 1. Identify the current Brocade SANnav version installed in your environment
  2. 2. Download the fixed version (SANnav version 2.2.2a or later/2.3.0) from Broadcom support portal (support.broadcom.com)
  3. 3. Review Broadcom upgrade documentation and release notes for SANnav
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Perform a complete backup of the current SANnav installation and configuration
  6. 6. Follow the standard SANnav upgrade procedure as documented by Broadcom
  7. 7. After upgrade, verify that the sensitive fields are now properly masked in configuration logs
  8. 8. If using 'supportsave' outputs, ensure any previously collected outputs with exposed sensitive data are securely destroyed or re-collected
Caveat Review Broadcom release notes for any configuration or feature changes between your current version and the upgrade target

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-2023-31423 — 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-2023-31423 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