Brocade Sannav vulnerabilities
34 vulnerabilities
Known vulnerabilities in Brocade Sannav, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2025-1053broadcombrocade_sannav+1
EPSS score0.16%
Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obtained from a Brocade SANnav supportsave. An attacker with privileged access to the Brocade SANnav database could use the encryption key to obtain passwords used by Brocade SANnav.CVE-2022-33187broadcombrocade_sannav+1EPSS score0.49%
Brocade SANnav before v2.2.1 logs usernames and encoded passwords in
debug-enabled logs. The vulnerability could allow an attacker with admin
privilege to read sensitive information.CVE-2024-2860broadcombrocade_sannav+1EPSS score0.16%
The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect local authentication flaw. An attacker accessing the VM where the Brocade SANnav is installed can gain access to sensitive data inside the PostgreSQL database.CVE-2024-2240broadcombrocade_sannav+1EPSS score0.51%
Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could allow a remote authenticated attacker to execute various attacks.CVE-2024-2859broadcombrocade_sannav+1EPSS score0.85%
By default, SANnav OVA is shipped with root user login enabled. While protected by a password, access to root could expose SANnav to a remote attacker should they gain access to the root account.CVE-2024-4159broadcombrocade_sannav+1EPSS score0.52%
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.CVE-2024-4173broadcombrocade_sannav+1EPSS score0.59%
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.CVE-2024-4282broadcombrocade_sannav+1EPSS score0.29%
Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.CVE-2024-4161broadcombrocade_sannav+1EPSS score0.47%
In Brocade SANnav, before Brocade SANnav v2.3.0, syslog traffic received
clear text. This could allow an unauthenticated, remote attacker to
capture sensitive information.CVE-2024-29964broadcombrocade_sannav+1EPSS score0.52%
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.CVE-2024-29965broadcombrocade_sannav+1EPSS score0.41%
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.CVE-2024-29958broadcombrocade_sannav+1EPSS score0.29%
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the encryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node. This could provide attackers an additional, less protected path to acquiring the encryption key.CVE-2024-29952broadcombrocade_sannav+1EPSS score0.11%
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to print the Auth, Priv, and SSL key store passwords in unencrypted logs by manipulating command variables.CVE-2024-29951broadcombrocade_sannav+1EPSS score0.16%
Brocade SANnav before v2.3.1 and v2.3.0a uses the SHA-1 hash in internal SSH ports that are not open to remote connection.CVE-2024-29968broadcombrocade_sannav+1EPSS score0.46%
An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Brocade SANnav instances are configured in disaster recovery mode. SQL Table names, column names, and SQL queries are collected in DR standby Supportsave. This could allow authenticated users to access the database structure and its contents.CVE-2024-29956broadcombrocade_sannav+1EPSS score0.28%
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the Brocade SANnav password in clear text in supportsave logs when a user schedules a switch Supportsave from Brocade SANnav.CVE-2024-29963broadcombrocade_sannav+1EPSS score0.16%
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.CVE-2024-29969broadcombrocade_sannav+1EPSS score0.29%
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.CVE-2024-29966broadcombrocade_sannav+1EPSS score0.65%
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.CVE-2024-29959broadcombrocade_sannav+1EPSS score0.48%
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save.