CVE-2020-15382
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 before version 2.1.1 uses a hard-coded administrator account with the weak password ‘passw0rd’ if a password is not provided for PostgreSQL at install-time.
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 confidenceBrocade SANnav prior to version 2.1.1 contains a hard-coded administrator account with the weak default password 'passw0rd'. This account is created automatically during PostgreSQL installation if no password is provided at install-time, potentially allowing unauthorized administrative access to the SAN management system.
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.1.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 installation and versionLocate the SANnav installation directory and check the version file or use the SANnav management interface to view the installed version number. Common locations include /opt/sannav or the application data directory.Affected if The installed version is below 2.1.1
-
Access PostgreSQL database used by SANnavConnect to the PostgreSQL instance that backs SANnav. This is typically installed locally on the SANnav server. Use psql or a database client to connect to the sannav or postgres database.Affected if You are able to connect using default PostgreSQL credentials
-
Query for the hard-coded accountRun the SQL query: SELECT usename, passwd FROM pg_shadow WHERE usename = 'sannav' or similar administrator account names. Alternatively, attempt authentication with username 'sannav' and password 'passw0rd' against the PostgreSQL instance.Affected if An account exists with password 'passw0rd' or you successfully authenticate with those credentials
-
Verify password policy during installationReview installation scripts, configuration files, or documentation for the SANnav deployment to determine if a custom password was provided during PostgreSQL setup, or if the default weak password was allowed.Affected if No custom strong password was configured during PostgreSQL installation, leaving the default account accessible
A user is affected if SANnav version is below 2.1.1 AND the PostgreSQL database contains an account with the weak default password 'passw0rd' that can be used for unauthorized administrative access.
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.1.1
Upgrade Brocade SANnav to version 2.1.1 or later, and ensure strong, unique passwords are configured for all database accounts during installation. If already deployed, audit for the presence of the default account and rotate credentials immediately.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2020-15382 — 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-2020-15382 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