Overview 817 matches · 42 in Waratek scope · 9 protected · 5 exploited · 5 CISA KEV · 77 public PoC · 32 EPSS ≥ 0.5
817matches
42in Waratek scope5.1%
9protected1.1%
5exploited0.6%
5CISA KEV0.6%
77public PoC9.4%
32EPSS ≥ 0.53.9%
Protected by Waratek
9
1.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
33
4.0%
Outside Waratek scope
40
4.9%
Not applicable
735
90.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
9
1.1%
partly blocked
0
0.0%
not blocked
808
98.9%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 198 / year
19981
Not applicable1
Medium1
not blocked1
No public exploit1
19993
Not applicable3
High2
Medium1
not blocked3
No public exploit3
20003
Not applicable3
High2
Low1
not blocked3
Working exploit published2
No public exploit1
20015
Not applicable5
High3
Medium1
Low1
not blocked5
Working exploit published1
No public exploit4
20022
Not applicable2
Medium2
not blocked2
No public exploit2
20030
200410
Not applicable10
High2
Medium6
Low2
not blocked10
No public exploit10
200529
Not applicable29
High19
Medium10
not blocked29
Working exploit published14
No public exploit15
200622
Not applicable22
High15
Medium7
not blocked22
Working exploit published9
No public exploit13
200747
Not applicable47
High35
Medium11
Low1
not blocked47
Working exploit published13
No public exploit34
200815
Not applicable15
High10
Medium5
not blocked15
Working exploit published3
No public exploit12
20094
Not applicable4
High2
Medium2
not blocked4
Working exploit published1
No public exploit3
20102
Outside Waratek scope1
Not applicable1
High2
not blocked2
Working exploit published1
No public exploit1
20118
Not applicable8
High6
Medium2
not blocked8
Working exploit published1
No public exploit7
20124
Not applicable4
High3
Medium1
not blocked4
Working exploit published1
No public exploit3
20132
Not applicable2
Medium2
not blocked2
No public exploit2
20148
Not applicable8
High3
Medium5
not blocked8
Exploited1
Working exploit published2
No public exploit5
201510
Not applicable10
High3
Medium5
Low2
not blocked10
Working exploit published4
No public exploit6
201612
Not applicable12
Critical3
High6
Medium3
not blocked12
No public exploit12
201722
No exploit published2
Not applicable20
Critical4
High11
Medium7
not blocked22
Working exploit published5
No public exploit17
201848
Protected by Waratek2
No exploit published1
Not applicable45
Critical11
High22
Medium15
blocked by ARMR today2
not blocked46
Exploited1
Working exploit published5
No public exploit42
201939
Protected by Waratek2
No exploit published1
Outside Waratek scope12
Not applicable24
Critical10
High20
Medium8
Low1
blocked by ARMR today2
not blocked37
No public exploit39
202061
No exploit published3
Outside Waratek scope9
Not applicable49
Critical10
High27
Medium23
Low1
not blocked61
Working exploit published3
Proof of concept only3
Forecast only1
No public exploit54
202150
Outside Waratek scope14
Not applicable36
Critical6
High21
Medium23
not blocked50
Exploited2
Proof of concept only4
Forecast only2
No public exploit42
202268
Protected by Waratek2
No exploit published1
Outside Waratek scope1
Not applicable64
Critical11
High32
Medium24
Low1
blocked by ARMR today2
not blocked66
Proof of concept only5
Forecast only1
No public exploit62
202365
No exploit published2
Not applicable63
Critical13
High29
Medium23
not blocked65
Working exploit published1
Proof of concept only10
No public exploit54
202447
Outside Waratek scope2
Not applicable45
Critical9
High17
Medium20
Low1
not blocked47
Proof of concept only3
No public exploit44
202532
Not applicable32
Critical1
High13
Medium13
Low5
not blocked32
Exploited1
Proof of concept only7
No public exploit24
2026198
Protected by Waratek3
No exploit published23
Outside Waratek scope1
Not applicable171
Critical7
High89
Medium84
Low18
blocked by ARMR today3
not blocked195
Working exploit published1
Proof of concept only27
No public exploit170
1999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-9649 | Low | 2025-08-29 | Not applicable | Proof of concept only | A security vulnerability has been detected in appneta tcpreplay 4.5.1. Impacted is the function calc_sleep_time of the file send_packets.c. Such manipulation leads to divide by zero. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. Upgrading to version 4.5.3-beta3 is recommended to address this issue. It is advisable to upgrade the affected component. The vendor confirms in a GitHub issue reply: "Was able to reproduce in 6fcbf03 but NOT 4.5.3-beta3." |
| CVE-2025-9386 | Low | 2025-08-24 | Not applicable | Proof of concept only | A vulnerability has been found in appneta tcpreplay up to 4.5.1. The impacted element is the function get_l2len_protocol of the file get.c of the component tcprewrite. Such manipulation leads to use after free. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. Upgrading to version 4.5.2-beta3 is sufficient to resolve this issue. You should upgrade the affected component. |
| CVE-2025-9385 | Low | 2025-08-24 | Not applicable | No public exploit | A flaw has been found in appneta tcpreplay up to 4.5.1. The affected element is the function fix_ipv6_checksums of the file edit_packet.c of the component tcprewrite. This manipulation causes use after free. The attack is restricted to local execution. The exploit has been published and may be used. Upgrading to version 4.5.2-beta3 is sufficient to fix this issue. It is advisable to upgrade the affected component. |
| CVE-2025-9384 | Low | 2025-08-24 | Not applicable | Proof of concept only | A vulnerability was detected in appneta tcpreplay up to 4.5.1. Impacted is the function tcpedit_post_args of the file /src/tcpedit/parse_args.c. The manipulation results in null pointer dereference. The attack is only possible with local access. The exploit is now public and may be used. Upgrading to version 4.5.2-beta2 is recommended to address this issue. Upgrading the affected component is advised. The vendor explains, that he was "[a]ble to reproduce in 6fcbf03 but not in 4.5.2-beta2". |
| CVE-2025-9019 | Low | 2025-08-15 | Not applicable | Proof of concept only | A vulnerability has been found in tcpreplay 4.5.1. This vulnerability affects the function mask_cidr6 of the file cidr.c of the component tcpprep. The manipulation leads to heap-based buffer overflow. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The researcher is able to reproduce this with the latest official release 4.5.1 and the current master branch. The code maintainer cannot reproduce this for 4.5.2-beta1. In his reply the maintainer explains that "[i]n that case, this is a duplicate that was fixed in 4.5.2." |
| CVE-2025-8661 | Medium | 2025-08-11 | Not applicable | No public exploit | A stored Cross-Site Scripting vulnerability (XSS) occurs when the server does not properly validate or encode the data entered by the user. |
| CVE-2025-8660 | Medium | 2025-08-11 | Not applicable | No public exploit | Privilege escalation occurs when a user gets access to more resources or functionality than they are normally allowed. |
| CVE-2025-7398 | High | 2025-07-17 | Not applicable | No public exploit | Brocade ASCG before 3.3.0 allows for the use of medium strength cryptography algorithms on internal ports ports 9000 and 8036. |
| CVE-2025-6391 | High | 2025-07-17 | Not applicable | No public exploit | Brocade ASCG before 3.3.0 logs JSON Web Tokens (JWT) in log files. An attacker with access to the log files can withdraw the unencrypted tokens with security implications, such as unauthorized access, session hijacking, and information disclosure. |
| 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-2025-4663 | Medium | 2025-07-08 | Not applicable | No public exploit | An Improper Check for Unusual or Exceptional Conditions vulnerability in Brocade Fabric OS before 9.2.2.a could allow an authenticated, network-based attacker to cause a Denial-of-Service (DoS). The vulnerability is encountered when supportsave is invoked remotely, using ssh command or SANnav inline ssh, and the corresponding ssh session is terminated with Control C (^c ) before supportsave completion. This issue affects Brocade Fabric OS 9.0.0 through 9.2.2 |
| CVE-2025-50200 | Medium | 2025-06-19 | Not applicable | No public exploit | RabbitMQ is a messaging and streaming broker. In versions 3.13.7 and prior, RabbitMQ is logging authorization headers in plaintext encoded in base64. When querying RabbitMQ api with HTTP/s with basic authentication it creates logs with all headers in request, including authorization headers which show base64 encoded username:password. This is easy to decode and afterwards could be used to obtain control to the system depending on credentials. This issue has been patched in version 4.0.8. |
| CVE-2025-4661 | Medium | 2025-06-19 | Not applicable | No public exploit | A path transversal vulnerability in Brocade Fabric OS 9.1.0 through 9.2.2 could allow a local admin user to gain access to files outside the intended directory potentially leading to the disclosure of sensitive information. Note: Admin level privilege is required on the switch in order to exploit |
| CVE-2025-22245 | Medium | 2025-06-04 | Not applicable | No public exploit | VMware NSX contains a stored Cross-Site Scripting (XSS) vulnerability in the router port due to improper input validation. |
| CVE-2025-22244 | Medium | 2025-06-04 | Not applicable | No public exploit | VMware NSX contains a stored Cross-Site Scripting (XSS) vulnerability in the gateway firewall due to improper input validation. |
| CVE-2025-22243 | High | 2025-06-04 | Not applicable | No public exploit | VMware NSX Manager UI is vulnerable to a stored Cross-Site Scripting (XSS) attack due to improper input validation. |
| CVE-2024-22654 | High | 2025-05-29 | Not applicable | Proof of concept only | tcpreplay v4.4.4 was discovered to contain an infinite loop via the tcprewrite function at get.c. |
| CVE-2025-22248 | Critical | 2025-05-13 | Not applicable | No public exploit | The bitnami/pgpool Docker image, and the bitnami/postgres-ha k8s chart, under default configurations, comes with an 'repmgr' user that allows unauthenticated access to the database inside the cluster. The PGPOOL_SR_CHECK_USER is the user that Pgpool itself uses to perform streaming replication checks against nodes, and should not be at trust level. This allows to log into a PostgreSQL database using the repgmr user without authentication. If Pgpool is exposed externally, a potential attacker could use this user to get access to the service. This is also present within the bitnami/postgres-ha Kubernetes Helm chart. |
| CVE-2025-3599 | High | 2025-04-30 | Not applicable | No public exploit | Symantec Endpoint Protection Windows Agent, running an ERASER Engine prior to 119.1.7.8, may be susceptible to an Elevation of Privilege vulnerability, which may allow an attacker to delete resources that are normally protected from an application or user. |
| CVE-2025-1976 | High | 2025-04-24 | Not applicable | Exploited | Brocade Fabric OS versions starting with 9.1.0 have root access removed, however, a local user with admin privilege can potentially execute arbitrary code with full root privileges on Fabric OS versions 9.1.0 through 9.1.1d6. |
| CVE-2024-1509 | High | 2025-02-28 | Not applicable | No public exploit | Brocade ASCG before 3.2.0 Web Interface is not enforcing HSTS, as defined by RFC 6797. HSTS is an optional response header that can be configured on the server to instruct the browser to only communicate via HTTPS. The lack of HSTS allows downgrade attacks, SSL-stripping man-in-the-middle attacks, and weakens cookie-hijacking protections. |
| CVE-2024-5462 | Medium | 2025-02-15 | Not applicable | No public exploit | If Brocade Fabric OS before Fabric OS 9.2.0 configuration settings are not set to encrypt SNMP passwords, then the SNMP privsecret / authsecret fields can be exposed in plaintext. The plaintext passwords can be exposed in a configupload capture or a supportsave capture if encryption of passwords is not enabled. An attacker can use these passwords to fetch values of the supported OIDs via SNMPv3 queries. There are also a limited number of MIB objects that can be modified. |
| CVE-2024-5461 | High | 2025-02-15 | Not applicable | No public exploit | Implementation of the Simple Network Management Protocol (SNMP) operating on the Brocade 6547 (FC5022) embedded switch blade, makes internal script calls to system.sh from within the SNMP binary. An authenticated attacker could perform command or parameter injection on SNMP operations that are only enabled on the Brocade 6547 (FC5022) embedded switch. This injection could allow the authenticated attacker to issue commands as Root. |
| 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-2024-7517 | High | 2024-11-21 | Not applicable | No public exploit | A command injection vulnerability in Brocade Fabric OS before 9.2.0c, and 9.2.1 through 9.2.1a on IP extension platforms could allow a local authenticated attacker to perform a privileged escalation via crafted use of the portcfg command. This specific exploitation is only possible on IP Extension platforms: Brocade 7810, Brocade 7840, Brocade 7850 and on Brocade X6 or X7 directors with an SX-6 Extension blade installed. The attacker must be logged into the switch via SSH or serial console to conduct the attack. |
| CVE-2024-10403 | Medium | 2024-11-21 | Not applicable | No public exploit | Brocade Fabric OS versions before 8.2.3e2, versions 9.0.0 through 9.2.0c, and 9.2.1 through 9.2.1a can capture the SFTP/FTP server password used for a firmware download operation initiated by SANnav or through WebEM in a weblinker core dump that is later captured via supportsave. |
| 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-7516 | High | 2024-11-12 | Not applicable | No public exploit | A vulnerability in Brocade Fabric OS versions before 9.2.2 could allow man-in-the-middle attackers to conduct remote Service Session Hijacking that may arise from the attacker's ability to forge an SSH key while the Brocade Fabric OS Switch is performing various remote operations initiated by a switch admin. |
| CVE-2024-38493 | Medium | 2024-07-15 | Not applicable | No public exploit | A reflected cross-site scripting (XSS) vulnerability exists in the PAM UI web interface. A remote attacker able to convince a PAM user to click on a specially crafted link to the PAM UI web interface could potentially execute arbitrary client-side code in the context of PAM UI. |
| 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-5460 | High | 2024-06-26 | Not applicable | No public exploit | A vulnerability in the default configuration of the Simple Network Management Protocol (SNMP) feature of Brocade Fabric OS versions before v9.0.0 could allow an authenticated, remote attacker to read data from an affected device via SNMP. The vulnerability is due to hard-coded, default community string in the configuration file for the SNMP daemon. An attacker could exploit this vulnerability by using the static community string in SNMP version 1 queries to an affected device. |
| CVE-2024-29954 | Medium | 2024-06-26 | Not applicable | No public exploit | A vulnerability in a password management API in Brocade Fabric OS versions before v9.2.1, v9.2.0b, v9.1.1d, and v8.2.3e prints sensitive information in log files. This could allow an authenticated user to view the server passwords for protocols such as scp and sftp. Detail. When the firmwaredownload command is incorrectly entered or points to an erroneous file, the firmware download log captures the failed command, including any password entered in the command line. |
| CVE-2024-29953 | Medium | 2024-06-26 | Not applicable | No public exploit | A vulnerability in the web interface in Brocade Fabric OS before v9.2.1, v9.2.0b, and v9.1.1d prints encoded session passwords on session storage for Virtual Fabric platforms. This could allow an authenticated user to view other users' session encoded passwords. |
| 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-5973 | Medium | 2024-04-05 | Not applicable | No public exploit | Brocade Web Interface in Brocade Fabric OS v9.x and before v9.2.0 does not properly represent the portName to the user if the portName contains reserved characters. This could allow an authenticated user to alter the UI of the Brocade Switch and change ports display. |
| CVE-2024-24795 | Medium | 2024-04-04 | Outside Waratek scope | No public exploit | HTTP Response splitting in multiple modules in Apache HTTP Server allows an attacker that can inject malicious response headers into backend applications to cause an HTTP desynchronization attack. Users are recommended to upgrade to version 2.4.59, which fixes this issue. |
| CVE-2023-38709 | High | 2024-04-04 | Outside Waratek scope | Proof of concept only | Faulty input validation in the core of Apache allows malicious or exploitable backend/content generators to split HTTP responses. This issue affects Apache HTTP Server: through 2.4.58. |
| CVE-2023-3454 | Critical | 2024-04-04 | Not applicable | No public exploit | Remote code execution (RCE) vulnerability in Brocade Fabric OS after v9.0 and before v9.2.0 could allow an attacker to execute arbitrary code and use this to gain root access to the Brocade switch. |
| CVE-2024-3024 | High | 2024-03-28 | Not applicable | Proof of concept only | A vulnerability was found in appneta tcpreplay up to 4.4.4. It has been classified as problematic. This affects the function get_layer4_v6 of the file /tcpreplay/src/common/get.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The identifier VDB-258333 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2023-43279 | Medium | 2024-03-12 | Not applicable | No public exploit | Null Pointer Dereference in mask_cidr6 component at cidr.c in Tcpreplay 4.4.4 allows attackers to crash the application via crafted tcprewrite command. |
| CVE-2024-23617 | Critical | 2024-01-26 | Not applicable | No public exploit | A buffer overflow vulnerability exists in Symantec Data Loss Prevention version 14.0.2 and before. A remote, unauthenticated attacker can exploit this vulnerability by enticing a user to open a crafted document to achieve code execution. |
| CVE-2024-23616 | Critical | 2024-01-26 | Not applicable | No public exploit | A buffer overflow vulnerability exists in Symantec Server Management Suite version 7.9 and before. A remote, anonymous attacker can exploit this vulnerability to achieve remote code execution as SYSTEM. |
| CVE-2024-23615 | Critical | 2024-01-26 | Not applicable | No public exploit | A buffer overflow vulnerability exists in Symantec Messaging Gateway versions 10.5 and before. A remote, anonymous attacker can exploit this vulnerability to achieve remote code execution as root. |
| CVE-2024-23614 | Critical | 2024-01-26 | Not applicable | No public exploit | A buffer overflow vulnerability exists in Symantec Messaging Gateway versions 9.5 and before. A remote, anonymous attacker can exploit this vulnerability to achieve remote code execution as root. |
| CVE-2024-23613 | Critical | 2024-01-26 | Not applicable | No public exploit | A buffer overflow vulnerability exists in Symantec Deployment Solution version 7.9 when parsing UpdateComputer tokens. A remote, anonymous attacker can exploit this vulnerability to achieve remote code execution as SYSTEM. |
| CVE-2023-4256 | Medium | 2023-12-21 | Not applicable | No public exploit | Within tcpreplay's tcprewrite, a double free vulnerability has been identified in the tcpedit_dlt_cleanup() function within plugins/dlt_plugins.c. This vulnerability can be exploited by supplying a specifically crafted file to the tcprewrite binary. This flaw enables a local attacker to initiate a Denial of Service (DoS) attack. |
| CVE-2021-27795 | High | 2023-12-06 | Not applicable | No public exploit | Brocade Fabric OS (FOS) hardware platforms running any version of Brocade Fabric OS software, which supports the license string format; contain cryptographic issues that could allow for the installation of forged or fraudulent license keys. This would allow attackers or a malicious party to forge a counterfeit license key that the Brocade Fabric OS platform would authenticate and activate as if it were a legitimate license key. |
| CVE-2023-34054 | High | 2023-11-28 | No exploit published | No public exploit | In Reactor Netty HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition. Specifically, an application is vulnerable if Reactor Netty HTTP Server built-in integration with Micrometer is enabled. |
| CVE-2023-34062 | High | 2023-11-15 | No exploit published | No public exploit | In Reactor Netty HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, a malicious user can send a request using a specially crafted URL that can lead to a directory traversal attack. Specifically, an application is vulnerable if Reactor Netty HTTP Server is configured to serve static resources. |
| CVE-2023-37790 | Medium | 2023-11-09 | Not applicable | Proof of concept only | Jaspersoft Clarity PPM version 14.3.0.298 was discovered to contain an arbitrary file upload vulnerability via the Profile Picture Upload function. |
| CVE-2023-31096 | High | 2023-10-10 | Not applicable | Proof of concept only | An issue was discovered in Broadcom) LSI PCI-SV92EX Soft Modem Kernel Driver through 2.2.100.1 (aka AGRSM64.sys). There is Local Privilege Escalation to SYSTEM via a Stack Overflow in RTLCopyMemory (IOCTL 0x1b2150). An attacker can exploit this to elevate privileges from a medium-integrity process to SYSTEM. This can also be used to bypass kernel-level protections such as AV or PPL, because exploit code runs with high-integrity privileges and can be used in coordinated BYOVD (bring your own vulnerable driver) ransomware campaigns. |
| CVE-2023-4163 | Medium | 2023-08-31 | Not applicable | No public exploit | In Brocade Fabric OS before v9.2.0a, a local authenticated privileged user can trigger a buffer overflow condition, leading to a kernel panic with large input to buffers in the portcfgfportbuffers command. |
| CVE-2023-4162 | Medium | 2023-08-31 | Not applicable | No public exploit | A segmentation fault can occur in Brocade Fabric OS after Brocade Fabric OS v9.0 and before Brocade Fabric OS v9.2.0a through the passwdcfg command. This could allow an authenticated privileged user local user to crash a Brocade Fabric OS swith using the cli “passwdcfg --set -expire -minDiff“. |
| CVE-2023-3489 | High | 2023-08-31 | Not applicable | No public exploit | The firmwaredownload command on Brocade Fabric OS v9.2.0 could log the FTP/SFTP/SCP server password in clear text in the SupportSave file when performing a downgrade from Fabric OS v9.2.0 to any earlier version of Fabric OS. |
| 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-2023-4345 | Medium | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable client-side control bypass leads to unauthorized data access for low privileged user |
| CVE-2023-4344 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable to insufficient randomness due to improper use of ssl.rnd to setup CIM connection |
| CVE-2023-4343 | High | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable due to exposure of sensitive password information in the URL as a URL search parameter |
| CVE-2023-4342 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable due to insecure defaults of lacking HTTP strict-transport-security policy |
| CVE-2023-4341 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller is vulnerable to Privilege escalation to root due to creation of insecure folders by Web GUI |
| CVE-2023-4340 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller is vulnerable to Privilege escalation by taking advantage of the Session prints in the log file |
| CVE-2023-4339 | High | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable to exposure of private keys used for CIM stored with insecure file permissions |
| CVE-2023-4338 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable due to insecure default of HTTP configuration that does not provide X-Content-Type-Options Headers |
| CVE-2023-4337 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable to improper session handling of managed servers on Gateway installation |
| CVE-2023-4336 | Critical | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller web interface is vulnerable due to insecure default of HTTP configuration that does not safeguard cookies with Secure attribute |
| CVE-2023-4335 | High | 2023-08-15 | Not applicable | No public exploit | Broadcom RAID Controller Web server (nginx) is serving private server-side files without any authentication on Linux |