CVE-2024-4159: Protection mechanisms
Published Apr 25, 2024
·Updated
Brocade SANnav before v2.3.0a lacks protection mechanisms on port 2377/TCP and 7946/TCP, which could allow an unauthenticated attacker to sniff the SANnav Docker information.
Affected Software
2 affected components
Broadcom Brocade Sannav<2.3.0a
Brocade SANNav<2.3.0a
Event History
Apr 25, 2024
CVE Published
via MITRE·01:58 AM
Data Sourced
via MITRE·01:58 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-4159?
CVE-2024-4159 has not been explicitly assigned a CVSS score, but it enables potential unauthorized access which is considered serious.
2
How do I fix CVE-2024-4159?
To mitigate CVE-2024-4159, upgrade to Brocade SANnav version 2.3.0a or later.
3
What ports are vulnerable in CVE-2024-4159?
CVE-2024-4159 involves vulnerabilities on ports 2377/TCP and 7946/TCP.
4
Can CVE-2024-4159 be exploited remotely?
Yes, CVE-2024-4159 can be exploited remotely by unauthenticated attackers.
5
What information could be exposed due to CVE-2024-4159?
CVE-2024-4159 could allow attackers to sniff Docker information associated with SANnav.