CVE-2019-16210
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 · uneditedBrocade SANnav versions before v2.0, logs plain text database connection password while triggering support save.
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 confidenceIn Brocade SANnav versions prior to 2.0, the support save feature (used for generating support bundles/logs) writes the database connection password to log files in plain text. Any user or process with access to those logs can retrieve the database 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< 2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SANnav versionCheck the installed Brocade SANnav version. This is typically visible in the SANnav web interface login page, in the product UI (usually under Help > About), or via the installation files. If SANnav is deployed as a virtual appliance, check the VM console or running version. Compare this version to the affected range: any version prior to 2.0 is affected.Affected if The installed version is SANnav versions prior to 2.0 (for example, 1.x.x releases).
-
Locate support save output filesIdentify the directory where the support save feature stores its output. This is typically found in the SANnav installation directory or a designated logs directory. The support save feature generates support bundles containing log files. Common locations include: installation logs folder, support bundle export location, or default log directories configured during SANnav setup. Look for files with names like 'support_save', 'support_bundle', or timestamped archive files (.zip, .tar).Affected if Support save feature has been used and output files exist in the environment.
-
Inspect log files for plain text passwordsSearch within the support save output files (especially log files within the bundles) for the database connection password. Look for patterns such as 'password=', 'dbpassword', 'DatabasePassword', or similar fields containing the database password value in plain text (not hashed or masked). Extract and examine the logs from the support bundle.Affected if The database connection password appears in plain text within any of the support save log files.
You are affected if you are running any version of Brocade SANnav prior to 2.0 AND the support save feature has been used, resulting in log files that contain the database password in plain text.
Generated from the published advisory. Verify against your own configuration.
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 data2.0
Upgrade to SANnav v2.0 or later where the password is no longer logged in plain text; if upgrading is not immediately possible, restrict access to support save output files and implement log monitoring to detect unauthorized access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-16210 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-16210 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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