CVSS: 10.0EPSS: 0%CPEs: 1EXPL: 0CVE-2024-4173 – SANnav versions exposes Kafka in the wan interface.
https://notcve.org/view.php?id=CVE-2024-4173
25 Apr 2024 — A vulnerability in Brocade SANnav exposes Kafka in the wan interface. The vulnerability could allow an unauthenticated attacker to perform various attacks, including DOS against the Brocade SANnav. Una vulnerabilidad en las versiones ova de Brocade SANnav anteriores a Brocade SANnav v2.3.1 y v2.3.0a expone a Kafka en la interfaz wan. La vulnerabilidad podría permitir que un atacante no autenticado realice varios ataques, incluido DOS, el dispositivo Brocade SANnav. • https://support.broadcom.com/external/content/SecurityAdvisories/0/23285 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29969 – TLS/SSL weak message authentication code ciphers are added by default for port 18082
https://notcve.org/view.php?id=CVE-2024-29969
19 Apr 2024 — 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. Cuando se actualiza una instalación de Brocade SANnav de Brocade SANnav v2.2.2 a Brocade SANnav 2.3.0, los cifrados de códigos de autenticación de mensajes débiles TLS/SSL se agregan de forma predeterminada para el puerto 18082. • https://support.broadcom.com/external/content/SecurityAdvisories/0/23251 • CWE-326: Inadequate Encryption Strength •
CVSS: 6.0EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29967 – In Brocade SANnav before v2.31 and v2.3.0a, it was observed that Docker instances inside the appliance have insecure mount points
https://notcve.org/view.php?id=CVE-2024-29967
19 Apr 2024 — In Brocade SANnav before Brocade SANnav v2.31 and v2.3.0a, it was observed that Docker instances inside the appliance have insecure mount points, allowing reading and writing access to sensitive files. The vulnerability could allow a sudo privileged user on the host OS to read and write access to these files. En Brocade SANnav anterior a Brocade SANnav v2.31 y v2.3.0a, se observó que las instancias de Docker dentro del dispositivo tenían puntos de montaje inseguros, lo que permitía acceso de lectura y escri... • https://support.broadcom.com/external/content/SecurityAdvisories/0/23254 • CWE-276: Incorrect Default Permissions •
CVSS: 10.0EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29966 – hard-coded credentials in the documentation that appear as the appliance root password
https://notcve.org/view.php?id=CVE-2024-29966
19 Apr 2024 — Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance's root password. The vulnerability could allow an unauthenticated attacker full access to the Brocade SANnav appliance. Brocade SANnav OVA anterior a v2.3.1 y v2.3.0a contiene credenciales codificadas en la documentación que aparecen como la contraseña raíz del dispositivo. La vulnerabilidad podría permitir a un atacante no autenticado acceso completo al dispositivo Brocade SANnav. • https://support.broadcom.com/external/content/SecurityAdvisories/0/23255 • CWE-798: Use of Hard-coded Credentials •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29965 – Insecure backup
https://notcve.org/view.php?id=CVE-2024-29965
19 Apr 2024 — In Brocade SANnav before v2.3.1, and v2.3.0a, it is possible to back up the appliance from the web interface or the command line interface ("SSH"). The resulting backups are world-readable. A local attacker can recover backup files, restore them to a new malicious appliance, and retrieve the passwords of all the switches. En Brocade SANnav anterior a v2.3.1 y v2.3.0a, es posible realizar una copia de seguridad del dispositivo desde la interfaz web o la interfaz de línea de comandos ("SSH"). Las copias de se... • https://support.broadcom.com/external/content/SecurityAdvisories/0/23250 • CWE-922: Insecure Storage of Sensitive Information •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29964 – Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files
https://notcve.org/view.php?id=CVE-2024-29964
19 Apr 2024 — Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files. An unprivileged attacker who gains access to the server can read sensitive information from these files. Las instancias de Docker en Brocade SANnav anteriores a v2.3.1 y v2.3.0a tienen una arquitectura y configuración inseguras que generan múltiples vulnerabilidades. Los demonios de Docker están expuestos a la interfaz WAN y otras vulnerabilidades permiten un control total sobre el dispositivo Ova. Una ... • https://support.broadcom.com/external/content/SecurityAdvisories/0/23249 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-732: Incorrect Permission Assignment for Critical Resource •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29962 – Insecure file permission setting that makes files world-readable
https://notcve.org/view.php?id=CVE-2024-29962
19 Apr 2024 — Brocade SANnav OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes files world-readable. This could allow a local user without the required privileges to access sensitive information or a Java binary. Brocade SANnav OVA anteriores a v2.3.1 y v2.3.0a tienen una configuración de permisos de archivos inseguros que hace que los archivos sean legibles en todo el mundo. Esto podría permitir que un usuario local sin los privilegios necesarios acceda a información confidencial o a un b... • https://support.broadcom.com/external/content/SecurityAdvisories/0/23248 • CWE-276: Incorrect Default Permissions •
CVSS: 3.8EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29963 – Brocade SANnav contains hardcoded TLS keys used by Docker
https://notcve.org/view.php?id=CVE-2024-29963
19 Apr 2024 — 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. Brocade SANnav OVA anterior a v2.3.1 y v2.3.0a contiene claves codificadas utilizadas por Docker para acceder a registros remotos a través de TLS. Las conexiones TLS con una clave expuesta permiten a un atacante MITM el tráfico. Nota: Brocade SANnav no tiene acceso a registros Docker remotos. • https://support.broadcom.com/external/content/SecurityAdvisories/0/23247 • CWE-798: Use of Hard-coded Credentials •
CVSS: 8.5EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29961 – supply-chain attack risk
https://notcve.org/view.php?id=CVE-2024-29961
19 Apr 2024 — A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service to send ping commands in the background at regular intervals to gridgain.com to check if updates are available for the Component. This could make an unauthenticated, remote attacker aware of the behavior and launch a supply-chain attack against a Brocade SANnav appliance. Una vulnerabilidad afecta a Brocade SANnav anterior a v2.3.1 y v2.3.0a. Permite que un servicio Brocade SANnav envíe comandos de ping en s... • https://support.broadcom.com/external/content/SecurityAdvisories/0/23246 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2024-29960 – Identical SSH keys utilized inside the OVA image (CVE-2024-29960)
https://notcve.org/view.php?id=CVE-2024-29960
19 Apr 2024 — In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical in the VM every time SANnav is installed. Any Brocade SAnnav VM based on the official OVA images is vulnerable to MITM over SSH. An attacker can decrypt and compromise the SSH traffic to the SANnav. En las versiones del servidor Brocade SANnav anteriores a v2.3.1 y v2.3.0a, las claves SSH dentro de la imagen OVA están codificadas y son idénticas en la VM cada vez que se instala SANnav. Cualquier máquina virtu... • https://support.broadcom.com/external/content/SecurityAdvisories/0/23244 • CWE-798: Use of Hard-coded Credentials •