CVE-2024-29951: Brocade SANnav has weak encryption in internal SSH ports
First published: Wed Apr 17 2024(Updated: )
Brocade SANnav before v2.3.1 and v2.3.0a uses the SHA-1 hash in internal SSH ports that are not open to remote connection.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | <2.3.0a | |
| Broadcom SANnav OVA | <2.3.1 | |
| Broadcom SANnav OVA | =2.3.0a |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-29951?
CVE-2024-29951 is classified as a high severity vulnerability due to the use of the SHA-1 hash algorithm in Brocade SANnav.
How do I fix CVE-2024-29951?
To mitigate CVE-2024-29951, upgrade Brocade SANnav to version 2.3.1 or later.
What versions of Brocade SANnav are affected by CVE-2024-29951?
CVE-2024-29951 affects Brocade SANnav versions prior to 2.3.1 and specifically version 2.3.0a.
What is the impact of CVE-2024-29951 on Brocade SANnav users?
The impact of CVE-2024-29951 includes potential security risks associated with outdated hashing algorithms.
Is the internal SSH port affected by CVE-2024-29951 exposed externally?
No, the internal SSH ports affected by CVE-2024-29951 are not open to remote connection.
- agent/title
- agent/references
- agent/weakness
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- agent/severity
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/guess-ai
- vendor/broadcom
- canonical/broadcom sannav ova
- vendor/brocade