LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15382: Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password ‘passw0r...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Brocade SANnav versions before 2.1.1 can be installed with a hard-coded weak PostgreSQL administrator credential when no database password is supplied during setup. This creates a serious configuration-derived exposure for storage management environments, because a known privileged credential may exist without operators realizing it.

Executive priority

Prioritize this for storage environments running older SANnav, especially where management systems are network-accessible. The issue can undermine administrative control of infrastructure management software, but evidence in the bundle is incomplete on exploitation and technical reachability.

Technical view

The CVE describes Brocade SANnav before 2.1.1 using a hard-coded PostgreSQL administrator account password when the installer is not given a PostgreSQL password. The supplied sources do not provide CVSS, CWE, attack vector, or proof of exploitation details.

Likely exposure

Likely exposure is limited to Brocade SANnav deployments before 2.1.1 where PostgreSQL was installed without an explicit password. Risk increases if SANnav or its database services are reachable beyond a tightly controlled management network.

Exploitation context

The bundle does not cite active exploitation, and the CVE is not marked KEV. The main concern is unauthorized use of a known privileged database credential in affected installations, but the sources do not specify remote reachability or prerequisites.

Researcher notes

Key missing data includes CVSS vector, CWE mapping, precise authentication boundary, exploit prerequisites, and fixed-version behavior beyond the before-2.1.1 affected statement. Treat the vendor advisory as authoritative for remediation details.

Mitigation direction

  • Review the Broadcom advisory for the supported remediation path.
  • Upgrade affected SANnav deployments to version 2.1.1 or later if vendor guidance confirms.
  • Ensure PostgreSQL was installed with a unique strong password.
  • Restrict SANnav and database access to trusted management networks.
  • Rotate relevant database and administrator credentials after remediation.

Validation and detection

  • Inventory Brocade SANnav versions across storage management environments.
  • Identify installations created without an explicit PostgreSQL password.
  • Confirm whether SANnav or PostgreSQL services are reachable from untrusted networks.
  • Review authentication logs for unexpected PostgreSQL administrator access.
  • Verify remediation against Broadcom advisory guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15382 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aBrocade SANnavBrocade SANnav before version 2.1.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.