CVE-2024-29969: TLS/SSL weak message authentication code ciphers are added by default for port 18082
First published: Fri Apr 19 2024(Updated: )
When a Brocade SANnav installation is upgraded from Brocade SANnav v2.2.2 to Brocade SANnav 2.3.0, TLS/SSL weak message authentication code ciphers are added by default for port 18082.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | >=2.2.2<2.3.0a | |
| Broadcom SANnav OVA | >2.2.2<=2.3.0 |
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-29969?
CVE-2024-29969 has a medium severity rating due to the introduction of weak TLS/SSL ciphers.
How do I fix CVE-2024-29969?
To fix CVE-2024-29969, you should disable the weak message authentication code ciphers for port 18082 in Brocade SANnav.
Which versions of Brocade SANnav are affected by CVE-2024-29969?
Brocade SANnav versions between 2.2.2 and 2.3.0 are affected by CVE-2024-29969.
What vulnerabilities does CVE-2024-29969 introduce?
CVE-2024-29969 introduces vulnerabilities related to weak message authentication code ciphers that can be exploited for unauthorized access.
Is there a workaround for CVE-2024-29969?
Currently, the recommended workaround for CVE-2024-29969 is to manually configure secure ciphers and settings in Brocade SANnav.
- agent/title
- agent/references
- agent/weakness
- agent/type
- agent/first-publish-date
- agent/description
- agent/severity
- agent/author
- 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
- version/broadcom sannav ova/2.2.2
- vendor/brocade