SSH traffic compromise via cloned OVA keys
Published Apr 19, 2024 · Updated Aug 2, 2024
Hard-coded SSH host keys in Brocade SANnav before 2.3.0a and 2.3.1 allow attackers to decrypt SSH traffic via interception. The official OVA embeds the same SSH private keys in every appliance, so deployment clones them instead of generating installation-specific host keys. Exploitation requires an adjacent network position and high privileges, and it compromises the confidentiality and integrity of intercepted SSH sessions.
Summary
What happened
Hard-coded SSH host keys in Brocade SANnav before 2.3.0a and 2.3.1 allow attackers to decrypt SSH traffic via interception. The official OVA embeds the same SSH private keys in every appliance, so deployment clones them instead of generating installation-specific host keys. Exploitation requires an adjacent network position and high privileges, and it compromises the confidentiality and integrity of intercepted SSH sessions.
The record
- CVE
- CVE-2024-29960
- Published
- Apr 19, 2024
- Updated
- Aug 2, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- CWE-798, T1557
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Apr 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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