Remote traffic disclosure via static TLS ciphers
Published Jun 27, 2022 · Updated Aug 3, 2024
TLS cryptographic weakness in Brocade SANnav before 2.2.0.2 and 2.1.1.8 allows remote attackers to read protected traffic via ports 443 and 18082. The TLS configuration enables static-key cipher suites on those endpoints, weakening the protection of sessions that negotiate them. An attacker must reach an exposed SANnav endpoint and observe or obtain the resulting traffic; the advisory reports confidentiality impact without integrity or availability impact.
Summary
What happened
TLS cryptographic weakness in Brocade SANnav before 2.2.0.2 and 2.1.1.8 allows remote attackers to read protected traffic via ports 443 and 18082. The TLS configuration enables static-key cipher suites on those endpoints, weakening the protection of sessions that negotiate them. An attacker must reach an exposed SANnav endpoint and observe or obtain the resulting traffic; the advisory reports confidentiality impact without integrity or availability impact.
The record
- CVE
- CVE-2022-28166
- Published
- Jun 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Broadcom
- Product
- Brocade SANnav
- Classifications
- CWE-327, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=versions before v2.2.0.2 and v2.1.1.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo