CVE-2024-29963: Brocade SANnav contains hardcoded TLS keys used by Docker
First published: Fri Apr 19 2024(Updated: )
Brocade SANnav OVA before v2.3.1, and v2.3.0a, contain hardcoded TLS keys used by Docker. Note: Brocade SANnav doesn't have access to remote Docker registries.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | <2.3.0a | |
| Broadcom SANnav OVA | <2.3.1 | |
| Broadcom SANnav OVA |
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-29963?
CVE-2024-29963 is classified as a high-severity vulnerability due to hardcoded TLS keys in Brocade SANnav.
How do I fix CVE-2024-29963?
To mitigate CVE-2024-29963, upgrade Brocade SANnav to version 2.3.1 or later.
Which versions of Brocade SANnav are affected by CVE-2024-29963?
Brocade SANnav versions prior to 2.3.1 and 2.3.0a are affected by CVE-2024-29963.
What impact does CVE-2024-29963 have on Docker usage?
CVE-2024-29963 impacts Docker by exposing hardcoded TLS keys, which could lead to secure communication vulnerabilities.
Does Brocade SANnav have access to remote Docker registries related to CVE-2024-29963?
Brocade SANnav does not have access to remote Docker registries, which limits the vulnerability's exploitability.
- agent/weakness
- agent/type
- agent/references
- agent/first-publish-date
- agent/author
- agent/event
- agent/title
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/last-modified-date
- agent/severity
- 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