dbcve.org
Brocade SannavApplication · Broadcom

CVE-2023-31925

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to 2.2.2a 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 before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords in plaintext. A privileged user could retrieve these credentials with knowledge and access to these log files. SNMP credentials could be seen in SANnav SupportSave if the capture is performed after an SNMP configuration failure causes an SNMP communication log dump.

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 stores SNMPv3 authentication passwords in plaintext within log files. When an SNMP configuration failure occurs, the resulting SNMP communication log dump exposes these credentials in SANnav SupportSave archives. A privileged user with file system or log access can retrieve these plaintext credentials.

MitigationUpgrade to SANnav v2.3.0 or v2.2.2a which addresses the plaintext credential storage. Until patched, restrict access to log files and SupportSave archives to minimize exposure risk.

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
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 installed version number. This is typically visible in the SANnav web interface under About or in the installation logs.
    Affected if The installed version is lower than 2.2.2a (e.g., 2.2.0, 2.1.x, etc.)
  2. Verify SNMPv3 configuration status
    Check the SANnav administrative interface or configuration files to determine if SNMPv3 is currently enabled and configured with authentication credentials.
    Affected if SNMPv3 is configured and active in the SANnav environment
  3. Examine SANnav log directories for plaintext credentials
    Search through SANnav log directories for log files that may contain SNMP communication failures. Look for entries containing plaintext SNMPv3 authentication passwords.
    Affected if Log files contain visible plaintext SNMPv3 passwords (look for fields like authPassword, privPassword, or similar in plain text)
  4. Inspect SupportSave archives for credential exposure
    If available, examine any SANnav SupportSave archives for log dump files that may have captured SNMP communication failures with exposed credentials.
    Affected if SupportSave archives contain log files with plaintext SNMPv3 credentials

You are affected if SANnav version is below 2.2.2a, SNMPv3 is configured, and log files or SupportSave archives contain plaintext SNMPv3 authentication 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.2.2a or later
Fixed in 2.2.2a
Interim mitigation

Upgrade to SANnav v2.3.0 or v2.2.2a which addresses the plaintext credential storage. Until patched, restrict access to log files and SupportSave archives to minimize exposure risk.

Recommended fix High confidence

SANnav v2.2.2a or v2.3.0 or later

  1. 1. Download the fixed SANnav version (v2.2.2a or v2.3.0 or later) from the Broadcom support portal at support.broadcom.com
  2. 2. Review the upgrade guide and release notes for SANnav to understand the upgrade procedure
  3. 3. Back up the current SANnav configuration and database before performing the upgrade
  4. 4. Follow the standard SANnav upgrade process to install the fixed version
  5. 5. After upgrade, verify that SNMPv3 credentials are no longer stored in plaintext in log files
  6. 6. If using SupportSave for diagnostics, ensure any captured logs do not contain plaintext credentials
Caveat Review SANnav release notes for any compatibility or configuration changes between your current version and the target version

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