Overview 79 matches · 2 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 3 EPSS ≥ 0.5
79matches
2in Waratek scope2.5%
2protected2.5%
0exploited0.0%
0CISA KEV0.0%
2public PoC2.5%
3EPSS ≥ 0.53.8%
Protected by Waratek
2
2.5%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
1
1.3%
Not applicable
76
96.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
2.5%
partly blocked
0
0.0%
not blocked
77
97.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
3
3.8%
Forecast only
1
1.3%
No public exploit
75
94.9%
split by
peak 29 / year
20196
Not applicable6
High4
Medium2
not blocked6
No public exploit6
20203
Not applicable3
Critical1
High1
Medium1
not blocked3
No public exploit3
20219
Not applicable9
Critical1
High5
Medium3
not blocked9
No public exploit9
202212
Protected by Waratek2
Outside Waratek scope1
Not applicable9
Critical3
High4
Medium4
Low1
blocked by ARMR today2
not blocked10
Proof of concept only2
Forecast only1
No public exploit9
20233
Not applicable3
Critical1
Medium2
not blocked3
No public exploit3
202429
Not applicable29
Critical3
High12
Medium13
Low1
not blocked29
Proof of concept only1
No public exploit28
20258
Not applicable8
High3
Medium5
not blocked8
No public exploit8
20269
Not applicable9
High4
Medium5
not blocked9
No public exploit9
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-5769 | Medium | 2026-10-08 | Not applicable | No public exploit | A vulnerability in Brocade SANnav before 3.0.1 can have the Brocade Fabric OS switch admin password captured in plaintext within a memory swap file on the server hosting the Brocade SANnav Virtual Machine (VM). This can happen when the SANnav server encounters an Out Of Memory (OOM) condition. The vulnerability could allow an authenticated admin user with access to the server hosting the SANnav to potentially view the memory swap file and access the password(s). |
| CVE-2026-5049 | Medium | 2026-10-08 | Not applicable | No public exploit | A path traversal vulnerability affects the The Zone Alias Import flow feature in Brocade SANnav before 3.0.0a. A local authenticated attacker can write an uploaded content outside the intended directory. |
| CVE-2026-5048 | Medium | 2026-10-08 | Not applicable | No public exploit | In Brocade SANnav before 3.0.0a, an SQL Injection vulnerability in various external API inventories have a vulnerability that allows an authenticated attacker to inject malicious data into some of the REST API -query parameters. |
| CVE-2026-5047 | High | 2026-10-08 | Not applicable | No public exploit | A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords. |
| CVE-2025-12774 | Medium | 2026-02-03 | Not applicable | No public exploit | A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. An attacker with access to Brocade SANnav supportsave file, could open the file and then obtain sensitive information such as details of database tables and encrypted passwords. |
| CVE-2025-12773 | High | 2026-02-03 | Not applicable | No public exploit | A vulnerability in update-reports-purge-settings.sh script logging for Brocade SANnav before 2.4.0a could allow the collection of SANnav database password in the system audit logs. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the Brocade SANnav database password. |
| CVE-2025-12772 | High | 2026-02-02 | Not applicable | No public exploit | Brocade SANnav before 2.4.0b logs the Brocade Fabric OS Switch admin password on the SANnav support save logs. When OOM occurs on a Brocade SANnav server, the call stack trace for the Brocade switch is also collected in the heap dump file which contains this switch password in clear text. The vulnerability could allow a remote authenticated attacker with admin privilege able to access the SANnav logs or the supportsave to read the switch admin password. |
| CVE-2025-12680 | Medium | 2026-02-02 | Not applicable | No public exploit | Brocade SANnav before Brocade SANnav 2.4.0b logs database passwords in clear text in the standby SANnav server, after disaster recovery failover. The vulnerability could allow a remote authenticated attacker with admin privilege able to access the SANnav logs or the supportsave to read the database password. |
| CVE-2025-12679 | High | 2026-02-02 | Not applicable | No public exploit | A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. Note: The vulnerability is only triggered during a migration and not in a new installation. The system audit logs are accessible only to a privileged user on the server. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user. |
| CVE-2025-6392 | Medium | 2025-07-10 | Not applicable | No public exploit | Brocade SANnav before Brocade SANnav 2.4.0a could log database passwords in clear text in audit logs when the daily data dump collector invokes docker exec commands. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user. |
| CVE-2025-6390 | Medium | 2025-07-10 | Not applicable | No public exploit | Brocade SANnav before SANnav 2.4.0a logs passwords and pbe keys in the Brocade SANnav server audit logs after installation and under specific conditions. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user. |
| CVE-2025-4662 | Medium | 2025-07-10 | Not applicable | No public exploit | Brocade SANnav before SANnav 2.4.0a logs plaintext passphrases in the Brocade SANnav host server audit logs while executing OpenSSL command using a passphrase from the command line or while providing the passphrase through a temporary file. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user. |
| CVE-2024-4282 | High | 2025-02-15 | Not applicable | No public exploit | Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22. |
| CVE-2024-10405 | Medium | 2025-02-15 | Not applicable | No public exploit | Brocade SANnav before SANnav 2.3.1b enables weak TLS ciphers on ports 443 and 18082. In case of a successful exploit, an attacker can read Brocade SANnav data stream that includes monitored Brocade Fabric OS switches performance data, port status, zoning information, WWNs, IP Addresses, but no customer data, no personal data and no secrets or passwords, as it travels across the network. |
| CVE-2025-1053 | High | 2025-02-14 | Not applicable | No public exploit | 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-2024-2240 | High | 2025-02-14 | Not applicable | No public exploit | 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-10404 | Medium | 2025-02-14 | Not applicable | No public exploit | CalInvocationHandler in Brocade SANnav before 2.3.1b logs sensitive information in clear text. The vulnerability could allow an authenticated, local attacker to view Brocade Fabric OS switch sensitive information in clear text. An attacker with administrative privileges could retrieve sensitive information including passwords; SNMP responses that contain AuthSecret and PrivSecret after collecting a “supportsave” or getting access to an already collected “supportsave”. NOTE: this issue exists because of an incomplete fix for CVE-2024-29952 |
| CVE-2022-43937 | Medium | 2024-11-21 | Not applicable | No public exploit | Possible information exposure through log file vulnerability where sensitive fields are recorded in the debug-enabled logs when debugging is turned on in Brocade SANnav before 2.3.0 and 2.2.2a |
| CVE-2022-43936 | Medium | 2024-11-21 | Not applicable | No public exploit | Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled. |
| CVE-2022-43935 | Medium | 2024-11-21 | Not applicable | No public exploit | An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where Brocade Fabric OS Switch passwords and authorization IDs are printed in the embedded MLS DB file. |
| CVE-2022-43934 | High | 2024-11-21 | Not applicable | No public exploit | Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095. |
| CVE-2022-43933 | Medium | 2024-11-21 | Not applicable | No public exploit | An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where configuration secrets are logged in supportsave. Supportsave file is generated by an admin user troubleshooting the switch. The Logged information may include usernames and passwords, and secret keys. |
| CVE-2024-3596 | Critical | 2024-07-09 | Not applicable | Proof of concept only | RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature. |
| CVE-2024-2860 | High | 2024-05-08 | Not applicable | No public exploit | 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-2859 | High | 2024-04-27 | Not applicable | No public exploit | 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-4173 | Critical | 2024-04-25 | Not applicable | No public exploit | 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-4161 | High | 2024-04-25 | Not applicable | No public exploit | 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-4159 | Medium | 2024-04-25 | Not applicable | No public exploit | 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-29969 | High | 2024-04-19 | Not applicable | No public exploit | 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-29968 | High | 2024-04-19 | Not applicable | No public exploit | 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-29967 | Medium | 2024-04-19 | Not applicable | No public exploit | 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. |
| CVE-2024-29966 | Critical | 2024-04-19 | Not applicable | No public exploit | 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-29965 | Medium | 2024-04-19 | Not applicable | No public exploit | 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-29964 | Medium | 2024-04-19 | Not applicable | No public exploit | 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-29963 | Low | 2024-04-19 | Not applicable | No public exploit | 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-29962 | Medium | 2024-04-19 | Not applicable | No public exploit | 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. |
| CVE-2024-29961 | High | 2024-04-19 | Not applicable | No public exploit | 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. |
| CVE-2024-29960 | High | 2024-04-19 | Not applicable | No public exploit | 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. |
| CVE-2024-29959 | High | 2024-04-19 | Not applicable | No public exploit | 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. |
| CVE-2024-29958 | High | 2024-04-19 | Not applicable | No public exploit | 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-29957 | High | 2024-04-19 | Not applicable | No public exploit | When Brocade SANnav before v2.3.1 and v2.3.0a servers are configured in Disaster Recovery mode, the encryption key is stored in the DR log files. This could provide attackers with an additional, less-protected path to acquiring the encryption key. |
| CVE-2024-29956 | Medium | 2024-04-18 | Not applicable | No public exploit | 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-29955 | Medium | 2024-04-17 | Not applicable | No public exploit | A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs. This could provide attackers with an additional, less-protected path to acquiring the encryption key. |
| CVE-2024-29952 | Medium | 2024-04-17 | Not applicable | No public exploit | 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-29951 | Medium | 2024-04-17 | Not applicable | No public exploit | 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-29950 | High | 2024-04-17 | Not applicable | No public exploit | The class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signature scheme, which has a SHA-1 hash. The vulnerability could allow a remote, unauthenticated attacker to perform a man-in-the-middle attack. |
| CVE-2023-31925 | Medium | 2023-08-31 | Not applicable | No public exploit | Brocade SANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords in plaintext. A privileged user could retrieve these credentials with knowledge and access to these log files. SNMP credentials could be seen in SANnav SupportSave if the capture is performed after an SNMP configuration failure causes an SNMP communication log dump. |
| CVE-2023-31424 | Critical | 2023-08-31 | Not applicable | No public exploit | Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2a allows remote unauthenticated users to bypass web authentication and authorization. |
| CVE-2023-31423 | Medium | 2023-08-31 | Not applicable | No public exploit | Possible information exposure through log file vulnerability where sensitive fields are recorded in the configuration log without masking on Brocade SANnav before v2.3.0 and 2.2.2a. Notes: To access the logs, the local attacker must have access to an already collected Brocade SANnav "supportsave" outputs. |
| CVE-2022-33187 | Medium | 2022-12-09 | Not applicable | No public exploit | 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-2022-28168 | High | 2022-06-27 | Not applicable | No public exploit | In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored using Base64 encoding, which could allow an attacker able to access log files to easily decode the passwords. |
| CVE-2022-28167 | Medium | 2022-06-27 | Not applicable | No public exploit | Brocade SANnav before Brocade SANvav v. 2.2.0.2 and Brocade SANanv v.2.1.1.8 logs the Brocade Fabric OS switch password in plain text in asyncjobscheduler-manager.log |
| CVE-2022-28166 | High | 2022-06-27 | Not applicable | No public exploit | In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Static Key Ciphers (ssl-static-key-ciphers) on ports 443 & 18082. |
| CVE-2022-2068 | Critical | 2022-06-21 | Outside Waratek scope | Proof of concept only | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). |
| CVE-2022-28162 | Low | 2022-05-09 | Not applicable | No public exploit | Brocade SANnav before version SANnav 2.2.0 logs the REST API Authentication token in plain text. |
| CVE-2022-28161 | Medium | 2022-05-09 | Not applicable | No public exploit | An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh passwords in filetansfer.log in debug mode. To exploit this vulnerability, the attacker would need to have valid user credentials and turn on debug mode. |
| CVE-2022-28165 | High | 2022-05-06 | Not applicable | No public exploit | A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an authenticated, remote attacker to access resources that they should not be able to access and perform actions that they should not be able to perform. The vulnerability exists because restrictions are not performed on Server side to ensure the user has required permission before processing requests. |
| CVE-2022-28164 | Medium | 2022-05-06 | Not applicable | No public exploit | Brocade SANnav before SANnav 2.2.0 application uses the Blowfish symmetric encryption algorithm for the storage of passwords. This could allow an authenticated attacker to decrypt stored account passwords. |
| CVE-2022-28163 | Critical | 2022-05-06 | Not applicable | No public exploit | In Brocade SANnav before Brocade SANnav 2.2.0, multiple endpoints associated with Zone management are susceptible to SQL injection, allowing an attacker to run arbitrary SQL commands. |
| CVE-2022-23305 | Critical | 2022-01-18 | Protected by Waratek | Proof of concept only | By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. |
| CVE-2022-23302 | High | 2022-01-18 | Protected by Waratek | Forecast only | JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. |
| CVE-2020-15387 | High | 2021-06-09 | Not applicable | No public exploit | The host SSH servers of Brocade Fabric OS before Brocade Fabric OS v7.4.2h, v8.2.1c, v8.2.2, v9.0.0, and Brocade SANnav before v2.1.1 utilize keys of less than 2048 bits, which may be vulnerable to man-in-the-middle attacks and/or insecure SSH communications. |
| CVE-2020-15385 | Medium | 2021-06-09 | Not applicable | No public exploit | Brocade SANnav before version 2.1.1 allows an authenticated attacker to list directories, and list files without permission. As a result, users without permission can see folders, and hidden files, and can create directories without permission. |
| CVE-2020-15384 | Medium | 2021-06-09 | Not applicable | No public exploit | Brocade SANNav before version 2.1.1 contains an information disclosure vulnerability. Successful exploitation of internal server information in the initial login response header. |
| CVE-2020-15382 | High | 2021-06-09 | Not applicable | No public exploit | Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password ‘passw0rd’ if a password is not provided for PostgreSQL at install-time. |
| CVE-2020-15381 | High | 2021-06-09 | Not applicable | No public exploit | Brocade SANnav before version 2.1.1 contains an Improper Authentication vulnerability that allows cleartext transmission of authentication credentials of the jmx server. |
| CVE-2020-15380 | High | 2021-06-09 | Not applicable | No public exploit | Brocade SANnav before version 2.1.1 logs account credentials at the ‘trace’ logging level. |
| CVE-2020-15379 | High | 2021-06-09 | Not applicable | No public exploit | Brocade SANnav before v.2.1.0a could allow remote attackers cause a denial-of-service condition due to a lack of proper validation, of the length of user-supplied data as name for custom field name. |
| CVE-2020-15378 | Medium | 2021-06-09 | Not applicable | No public exploit | The OVA version of Brocade SANnav before version 2.1.1 installation with IPv6 networking exposes the docker container ports to the network, increasing the potential attack surface. |
| CVE-2020-15377 | Critical | 2021-06-09 | Not applicable | No public exploit | Webtools in Brocade SANnav before version 2.1.1 allows unauthenticated users to make requests to arbitrary hosts due to a misconfiguration; this is commonly referred to as Server-Side Request Forgery (SSRF). |
| CVE-2019-16212 | High | 2020-09-25 | Not applicable | No public exploit | A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. The vulnerability could allow a remote attacker to bypass the authentication process. |
| CVE-2019-16211 | Critical | 2020-09-25 | Not applicable | No public exploit | Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability. |
| CVE-2020-13401 | Medium | 2020-06-02 | Not applicable | No public exploit | An issue was discovered in Docker Engine before 19.03.11. An attacker in a container, with the CAP_NET_RAW capability, can craft IPv6 router advertisements, and consequently spoof external IPv6 hosts, obtain sensitive information, or cause a denial of service. |
| CVE-2019-16210 | Medium | 2019-11-08 | Not applicable | No public exploit | Brocade SANnav versions before v2.0, logs plain text database connection password while triggering support save. |
| CVE-2019-16209 | High | 2019-11-08 | Not applicable | No public exploit | A vulnerability, in The ReportsTrustManager class of Brocade SANnav versions before v2.0, could allow an attacker to perform a man-in-the-middle attack against Secure Sockets Layer(SSL)connections. |
| CVE-2019-16208 | High | 2019-11-08 | Not applicable | No public exploit | Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.). |
| CVE-2019-16207 | High | 2019-11-08 | Not applicable | No public exploit | Brocade SANnav versions before v2.0 use a hard-coded password, which could allow local authenticated attackers to access a back-end database and gain privileges. |
| CVE-2019-16206 | Medium | 2019-11-08 | Not applicable | No public exploit | The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' logging level; which could allow a local authenticated attacker to access sensitive information. |
| CVE-2019-16205 | High | 2019-11-08 | Not applicable | No public exploit | A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID. The vulnerability is due to an insufficiently random session ID for several post-authentication actions in the SANnav portal. |