dbcve.org
SannavApplication · Broadcom

CVE-2025-12679

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-02
Fix available
A fix is available. Upgrade to 2.4.0b 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
A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. Note: The vulnerability is only triggered during a migration and not in a new installation. The system audit logs are accessible only to a privileged user on the server. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user.

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 before version 2.4.0b exposes the Password-Based Encryption (PBE) key in plaintext within system audit logs during migration operations. An authenticated attacker with access to the local server VM audit logs could retrieve this key. The vulnerability only triggers during migration, not fresh installations, and the logs are only accessible to server administrators, not SANnav users.

MitigationUpgrade to Brocade SANnav version 2.4.0b or later to resolve the plaintext PBE key exposure in audit logs. Since the vulnerability requires both authentication and privileged access to host server audit logs, ensure audit log access controls are properly configured as an additional safeguard.

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
SannavApplication
Affected:< 2.4.0b

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 installed SANnav version
    Locate SANnav installation and retrieve the version number from the application or system configuration
    Affected if Version is present and less than 2.4.0b
  2. Confirm migration was performed
    Determine whether a migration operation has ever been executed on this SANnav instance, as the flaw only triggers during migration, not fresh installations
    Affected if Migration operation was performed on the SANnav installation
  3. Locate system audit logs
    Access the local server VM audit logs that SANnav generates. These are typically found in the server's log directory accessible only to server administrators
    Affected if Audit logs exist and are accessible on the local server VM
  4. Search logs for plaintext PBE key
    Examine the audit logs for plaintext occurrences of the Password-Based Encryption (PBE) key string during the migration time period
    Affected if Audit logs contain the PBE key in plaintext format, indicating the vulnerability has been triggered

A system is affected if SANnav version is below 2.4.0b, a migration operation was performed, and the audit logs contain the PBE key in plaintext form.

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.4.0b or later
Fixed in 2.4.0b
Interim mitigation

Upgrade to Brocade SANnav version 2.4.0b or later to resolve the plaintext PBE key exposure in audit logs. Since the vulnerability requires both authentication and privileged access to host server audit logs, ensure audit log access controls are properly configured as an additional safeguard.

Recommended fix Moderate confidence

SANnav 2.4.0b or later

  1. 1. Identify the current SANnav version by accessing the SANnav management interface or checking the system information.
  2. 2. Plan for an upgrade to SANnav version 2.4.0b or later, as this version contains the fix for the plaintext PBE key logging vulnerability.
  3. 3. Review Broadcom's official upgrade documentation at support.broadcom.com for SANnav to ensure proper backup and migration procedures are followed.
  4. 4. Perform the upgrade following the documented upgrade path, noting that this vulnerability is only triggered during migration, not fresh installations.
  5. 5. After upgrading, verify the system is running version 2.4.0b or later.
  6. 6. During any subsequent migration, confirm that the PBE key is no longer printed in plaintext in the system audit logs.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sannav Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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