CVE-2024-4282: Weak TLS Ciphers on Brocade SANnav OVA SSH port 22
First published: Fri Feb 14 2025(Updated: )
Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom Brocade SANnav | <2.3.1b |
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-4282?
CVE-2024-4282 is considered a medium severity vulnerability due to the potential exposure of sensitive data.
How do I fix CVE-2024-4282?
To fix CVE-2024-4282, upgrade your Brocade SANnav OVA to version 2.3.1b or later.
What does CVE-2024-4282 affect?
CVE-2024-4282 affects Brocade SANnav OVA versions before 2.3.1b.
What is the risk of not addressing CVE-2024-4282?
Failing to address CVE-2024-4282 may lead to unauthorized access and potential data compromise through SSH.
Is there a workaround for CVE-2024-4282?
There are no official workarounds for CVE-2024-4282; upgrading is the recommended mitigation.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/title
- agent/weakness
- agent/description
- agent/type
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/severity
- agent/source
- agent/tags
- agent/last-modified-date
- agent/event
- vendor/brocade
- canonical/broadcom brocade sannav