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
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.
- Published
- Jun 27, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 45th percentile
- CWE
- CWE-327
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| broadcom | sannav | cpe:2.3:a:broadcom:sannav |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom sannavbefore 2.1.1.8
- broadcom sannav2.2.0.0 and later · before 2.2.0.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (brocade). Independent of NVD's CPE analysis and usually ahead of it.
n/a Brocade SANnav
- versions before v2.2.0.2 and v2.1.1.8affected
Same product
broadcom: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-28163In Brocade SANnav before Brocade SANnav 2.2.0, multiple endpoints associated with Zone management are susceptible to SQL injection, allowing39Monitor
- CVE-2020-15377Webtools in Brocade SANnav before version 2.1.1 allows unauthenticated users to make requests to arbitrary hosts due to a misconfiguration; 39Monitor
- CVE-2022-28165A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an authenticated, remot35Monitor
- CVE-2025-12772Plaintext Switch admin login password is seen in Brocade SANnav support save34Monitor
- CVE-2022-28168In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored using Base64 encoding, w30Monitor
- CVE-2020-15380Brocade SANnav before version 2.1.1 logs account credentials at the ‘trace’ logging level.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- security.netapp.com/advisory/ntap-20220627-0001/
- www.broadcom.com/support/fibre-channel-networking/security-advisories/brocade-security-advisory-2022-1977
Vendor advisories and official records. Exploit/PoC links are deliberately left out.