How severe is CVE-2019-16208?

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

Is CVE-2019-16208 being actively exploited?

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

What products are affected by CVE-2019-16208?

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

How do I fix CVE-2019-16208?

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-16208 published?

CVE-2019-16208 was published on 2019-11-08 and last updated on 2026-06-17.

CVE-2019-16208

CVE-2019-16208 is a high-severity vulnerability in Broadcom Brocade Sannav with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-327
Affected product: Broadcom Brocade Sannav
Published: 2019-11-08
Last modified: 2026-06-17

Description

Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.).

Frequently asked questions

What is CVE-2019-16208?: Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.).
How severe is CVE-2019-16208?: CVE-2019-16208 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-16208 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-16208?: CVE-2019-16208 affects Broadcom Brocade Sannav. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-16208?: 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-16208 published?: CVE-2019-16208 was published on 2019-11-08 and last updated on 2026-06-17.

References

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

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-16212 — High (CVSS 8.8): A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP…

All CVEs affecting Broadcom Brocade Sannav →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →