Overview 33 matches · 1 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 1 EPSS ≥ 0.5
33matches
1in Waratek scope3.0%
1protected3.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
1EPSS ≥ 0.53.0%
Protected by Waratek
1
3.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
32
97.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
3.0%
partly blocked
0
0.0%
not blocked
32
97.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
1
3.0%
No public exploit
32
97.0%
split by
peak 12 / year
20194
Not applicable4
High4
not blocked4
No public exploit4
20201
Not applicable1
High1
not blocked1
No public exploit1
20215
Not applicable5
High5
not blocked5
No public exploit5
20224
Protected by Waratek1
Not applicable3
High4
blocked by ARMR today1
not blocked3
Forecast only1
No public exploit3
20230
202412
Not applicable12
High12
not blocked12
No public exploit12
20253
Not applicable3
High3
not blocked3
No public exploit3
20264
Not applicable4
High4
not blocked4
No public exploit4
20192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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. |