SSH data exposure via enabled SHA-1 settings
Published Feb 14, 2025 · Updated Feb 18, 2025
Cryptographic weakness in Brocade SANnav before 2.3.1b allows remote attackers to expose SSH-protected data through SHA-1 collisions. The OVA's SSH service on TCP port 22 enables deprecated SHA-1 settings, permitting colliding inputs to produce the same hash value. Exploitation requires an SSH connection and a practical collision; the vendor reports no integrity or availability impact.
Summary
What happened
Cryptographic weakness in Brocade SANnav before 2.3.1b allows remote attackers to expose SSH-protected data through SHA-1 collisions. The OVA's SSH service on TCP port 22 enables deprecated SHA-1 settings, permitting colliding inputs to produce the same hash value. Exploitation requires an SSH connection and a practical collision; the vendor reports no integrity or availability impact.
The record
- CVE
- CVE-2024-4282
- Published
- Feb 14, 2025
- Updated
- Feb 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 18, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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