CVE-2024-29969: TLS/SSL weak message authentication code ciphers are added by default for port 18082
Published 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.
Affected Software
2 affected components
Broadcom Brocade Sannav>=2.2.2<2.3.0a
Brocade SANNav>2.2.2<=2.3.0
Event History
Apr 19, 2024
CVE Published
via MITRE·05:24 AM
Data Sourced
via MITRE·05:24 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
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.
2
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.
3
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.
4
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.
5
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.