dbcve.org
Brocade SannavApplication · Broadcom

CVE-2019-16212

HIGH · 8.8 CVSS v3.1 Published 2020-09-25
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. The vulnerability could allow a remote attacker to bypass the authentication process.

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

An LDAP injection vulnerability in Brocade SANnav versions before v2.1.0 allows a remote authenticated attacker to manipulate LDAP query parameters, potentially bypassing the authentication mechanism and gaining unauthorized access to the system.

MitigationUpgrade to Brocade SANnav v2.1.0 or later which contains the patch for this LDAP injection vulnerability.

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.1.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed SANnav version
    Access the SANnav administration interface and navigate to the About or System Information section to identify the current software version. Alternatively, check the installation package or release notes if available.
    Affected if The installed version is any release prior to 2.1.0 (e.g., 2.0.x, 1.x, etc.)
  2. Verify LDAP authentication is enabled
    In the SANnav admin console, navigate to Authentication Settings or User Management to determine whether LDAP-based authentication is configured as an active authentication method.
    Affected if LDAP authentication is enabled and the SANnav version is below 2.1.0
  3. Inspect LDAP user configuration
    Review the LDAP user or group mapping settings in SANnav to see how user queries are constructed. Look for any user-supplied parameters in the LDAP search filter or query fields.
    Affected if LDAP is enabled and the query configuration accepts user-modifiable input that could be injected

A system is affected if it runs any version of Brocade SANnav prior to 2.1.0 with LDAP authentication configured and active.

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.0 or later
Fixed in 2.1.0
Interim mitigation

Upgrade to Brocade SANnav v2.1.0 or later which contains the patch for this LDAP injection vulnerability.

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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