The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' log…

published 2019-11-08 7y ago modified 2026-06-17 4mo ago also EUVD-2019-7018

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits: 0; none known

The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' logging level; which could allow a local authenticated attacker to access sensitive information.

Patch / fix

fixed in 1

broadcom brocade_sannav 2.0

Is CVE-2019-16206 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Brocade Communications Systems, Inc. Brocade SANnav

Classification

Weakness

CWE-311 Missing Encryption of Sensitive Data
CWE-532 Insertion of Sensitive Information into Log File

References

broadcom.com /support/fibre-channel-networking/security-advisories/brocade-security-advisory-2019-865
vendor-advisory

Sources

CVE List CVE-2019-16206
NVD CVE-2019-16206

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.