Overview 35 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
35matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
35
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
35
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
35
100.0%
split by
peak 13 / year
20192
Not applicable2
Medium2
not blocked2
No public exploit2
20201
Not applicable1
Medium1
not blocked1
No public exploit1
20213
Not applicable3
Medium3
not blocked3
No public exploit3
20224
Not applicable4
Medium4
not blocked4
No public exploit4
20232
Not applicable2
Medium2
not blocked2
No public exploit2
202413
Not applicable13
Medium13
not blocked13
No public exploit13
20255
Not applicable5
Medium5
not blocked5
No public exploit5
20265
Not applicable5
Medium5
not blocked5
No public exploit5
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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. |