7.5
CWE
326
Advisory Published
Updated

CVE-2024-29950: Brocade SANnav before v2.3.1, v2.3.0a uses weak encryption

First published: Wed Apr 17 2024(Updated: )

The class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signature scheme, which has a SHA-1 hash. The vulnerability could allow a remote, unauthenticated attacker to perform a man-in-the-middle attack.

Credit: sirt@brocade.com

Affected SoftwareAffected VersionHow to fix
Broadcom SANnav OVA<2.3.0a
Broadcom SANnav OVA<2.3.1

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-29950?

    CVE-2024-29950 has a high severity rating due to the potential for remote, unauthenticated man-in-the-middle attacks.

  • How do I fix CVE-2024-29950?

    To fix CVE-2024-29950, upgrade Brocade SANnav to version 2.3.1 or later.

  • Which versions of Brocade SANnav are affected by CVE-2024-29950?

    Brocade SANnav versions prior to 2.3.1 and 2.3.0a are affected by CVE-2024-29950.

  • What type of attack can CVE-2024-29950 enable?

    CVE-2024-29950 can enable remote, unauthenticated man-in-the-middle attacks.

  • Is authentication needed to exploit CVE-2024-29950?

    No, CVE-2024-29950 can be exploited by remote, unauthenticated attackers.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203