How severe is CVE-2019-16212?

CVE-2019-16212 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-16212 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-16212?

CVE-2019-16212 affects Broadcom Brocade Sannav. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-16212?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-16212 published?

CVE-2019-16212 was published on 2020-09-25 and last updated on 2026-06-17.

CVE-2019-16212

CVE-2019-16212 is a high-severity vulnerability in Broadcom Brocade Sannav with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 1% (68th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Broadcom Brocade Sannav
Published: 2020-09-25
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2019-16212?: 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.
How severe is CVE-2019-16212?: CVE-2019-16212 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-16212 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-16212?: CVE-2019-16212 affects Broadcom Brocade Sannav. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-16212?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-16212 published?: CVE-2019-16212 was published on 2020-09-25 and last updated on 2026-06-17.

References

https://www.broadcom.com/support/fibre-channel-networking/security-advisories/brocade-security-advisory-2020-1074

Affected products (1)

cpe:2.3:a:broadcom:brocade_sannav:*:*:*:*:*:*:*:*

More vulnerabilities in Broadcom Brocade Sannav

CVE-2024-4282 — Critical (CVSS 9.8): Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.
CVE-2022-23305 — Critical (CVSS 9.8): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be…
CVE-2019-16211 — Critical (CVSS 9.8): Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability.
CVE-2024-3596 — Critical (CVSS 9.0): RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response…
CVE-2022-23302 — High (CVSS 8.8): JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write…
CVE-2019-16205 — High (CVSS 8.8): A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session…

All CVEs affecting Broadcom Brocade Sannav →