Confidentiality loss via SHA-1 on internal SSH
Published Apr 17, 2024 · Updated Aug 2, 2024
Weak cryptography in Brocade SANnav before 2.3.0a allows remote authenticated users to read confidential data through internal SSH ports. Those internal SSH services rely on SHA-1 hashing, but Broadcom has not disclosed which SSH negotiation or cryptographic operation applies the weak hash. Exploitation requires adjacent-network access and low privileges; the published impact is limited to confidentiality, with no integrity or availability impact.
Summary
What happened
Weak cryptography in Brocade SANnav before 2.3.0a allows remote authenticated users to read confidential data through internal SSH ports. Those internal SSH services rely on SHA-1 hashing, but Broadcom has not disclosed which SSH negotiation or cryptographic operation applies the weak hash. Exploitation requires adjacent-network access and low privileges; the published impact is limited to confidentiality, with no integrity or availability impact.
The record
- CVE
- CVE-2024-29951
- Published
- Apr 17, 2024
- Updated
- Aug 2, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- CWE-326
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 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=0 <2.3.0a
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.
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