CVE-2024-4159: Protection mechanisms
First published: Thu 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.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | <2.3.0a | |
| Broadcom SANnav OVA | <2.3.0a |
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-4159?
CVE-2024-4159 has not been explicitly assigned a CVSS score, but it enables potential unauthorized access which is considered serious.
How do I fix CVE-2024-4159?
To mitigate CVE-2024-4159, upgrade to Brocade SANnav version 2.3.0a or later.
What ports are vulnerable in CVE-2024-4159?
CVE-2024-4159 involves vulnerabilities on ports 2377/TCP and 7946/TCP.
Can CVE-2024-4159 be exploited remotely?
Yes, CVE-2024-4159 can be exploited remotely by unauthenticated attackers.
What information could be exposed due to CVE-2024-4159?
CVE-2024-4159 could allow attackers to sniff Docker information associated with SANnav.
- agent/title
- agent/references
- agent/type
- agent/weakness
- agent/first-publish-date
- agent/author
- agent/description
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/last-modified-date
- agent/severity
- agent/event
- 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
- vendor/brocade