CVE-2024-4282: Weak TLS Ciphers on Brocade SANnav OVA SSH port 22

Published Feb 14, 2025
·
Updated

Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.

Affected Software

2 affected components
Brocade SANnav OVA<2.3.1b
Broadcom Brocade Sannav<2.3.1b

Event History

Feb 14, 2025
CVE Published
via MITRE·11:33 PM
Data Sourced
via MITRE·11:33 PM
DescriptionWeakness
Feb 15, 2025
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

How do I fix CVE-2024-4282?

To fix CVE-2024-4282, upgrade your Brocade SANnav OVA to version 2.3.1b or later.

3

What does CVE-2024-4282 affect?

CVE-2024-4282 affects Brocade SANnav OVA versions before 2.3.1b.

4

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.

5

Is there a workaround for CVE-2024-4282?

There are no official workarounds for CVE-2024-4282; upgrading is the recommended mitigation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203