dbcve.org
Brocade SannavApplication · Broadcom

CVE-2019-16206

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-08
Fix available
A fix is available. Upgrade to 2.0 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
The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' logging level; which could allow a local authenticated attacker to access sensitive information.

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

In Brocade SANnav versions before v2.0, the authentication mechanism logs plaintext account credentials when logging is set to 'trace' or 'debug' levels. A local authenticated attacker with access to these log files can retrieve plaintext credentials for other accounts.

MitigationUpgrade to Brocade SANnav v2.0 or later to obtain the fixed authentication mechanism, or ensure logging levels are configured above 'trace' and 'debug' to prevent credential exposure in 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.0

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. Confirm Brocade SANnav installation
    Locate the Brocade SANnav installation directory or check system inventory for SANnav presence
    Affected if Brocade SANnav is installed on the system
  2. Identify SANnav version
    Use the SANnav management interface or run 'sannav -v' or check the installed packages to determine the version number
    Affected if The installed version is less than 2.0 (e.g., 1.x.x)
  3. Check logging configuration level
    Access SANnav admin console or configuration files and inspect the logging level setting
    Affected if Logging level is set to 'trace' or 'debug'
  4. Examine log files for credentials
    Locate SANnav log directories and search log files for plaintext password or credential patterns
    Affected if Log files contain plaintext credentials for user accounts

A user is affected if Brocade SANnav versions below 2.0 are installed AND logging is configured at 'trace' or 'debug' levels, potentially exposing plaintext credentials in 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.0 or later
Fixed in 2.0
Interim mitigation

Upgrade to Brocade SANnav v2.0 or later to obtain the fixed authentication mechanism, or ensure logging levels are configured above 'trace' and 'debug' to prevent credential exposure in logs.

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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