dbcve.org
SannavApplication · Broadcom

CVE-2020-15380

HIGH · 7.5 CVSS v3.1 Published 2021-06-09
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 version 2.1.1 logs account credentials at the ‘trace’ logging level.

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 prior to 2.1.1 contain a vulnerability where user account credentials are logged in plain text at the 'trace' logging level. This exposes sensitive authentication credentials in log files, which could be accessed by attackers who have access to the system logs.

MitigationUpgrade Brocade SANnav to version 2.1.1 or later to remediate this vulnerability. Additionally, review log files for any unauthorized access and rotate potentially exposed credentials.

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.1.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Locate the SANnav installation directory and check the version file or use the SANnav management interface to view the installed version information.
    Affected if The installed version is below 2.1.1 (for example, 2.0.x or earlier releases).
  2. Verify trace logging configuration
    Access the SANnav configuration settings and examine the logging configuration to determine if the 'trace' logging level is enabled.
    Affected if Trace-level logging is currently enabled in the logging configuration.
  3. Inspect log files for credential exposure
    Navigate to the SANnav log directory and search log files for patterns matching plain text credentials (look for keywords such as 'password', 'credential', or authentication tokens in plain text).
    Affected if Log files contain any plain text username/password combinations or authentication credentials.

A user is affected if their SANnav installation version is below 2.1.1 AND trace logging is enabled, which would result in credentials being written to log files.

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.

From vendor data
Upgrade available Upgrade to 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade Brocade SANnav to version 2.1.1 or later to remediate this vulnerability. Additionally, review log files for any unauthorized access and rotate potentially exposed credentials.

Fix this in Sannav Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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