Show filters
67 Total Results
Displaying 1-10 of 67
Sort by:
Attacker Value
Unknown
CVE-2022-2068
Disclosure Date: June 21, 2022 (last updated October 07, 2023)
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).
4
Attacker Value
Unknown
CVE-2024-4282
Disclosure Date: February 15, 2025 (last updated February 15, 2025)
Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.
0
Attacker Value
Unknown
CVE-2024-10405
Disclosure Date: February 15, 2025 (last updated February 15, 2025)
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.
0
Attacker Value
Unknown
CVE-2024-2240
Disclosure Date: February 14, 2025 (last updated February 14, 2025)
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.
0
Attacker Value
Unknown
CVE-2025-1053
Disclosure Date: February 14, 2025 (last updated February 14, 2025)
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.
0
Attacker Value
Unknown
CVE-2024-10404
Disclosure Date: February 14, 2025 (last updated February 14, 2025)
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
0
Attacker Value
Unknown
CVE-2022-43937
Disclosure Date: November 21, 2024 (last updated February 05, 2025)
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
0
Attacker Value
Unknown
CVE-2022-43936
Disclosure Date: November 21, 2024 (last updated February 05, 2025)
Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled.
0
Attacker Value
Unknown
CVE-2022-43935
Disclosure Date: November 21, 2024 (last updated February 05, 2025)
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.
0
Attacker Value
Unknown
CVE-2022-43934
Disclosure Date: November 21, 2024 (last updated February 05, 2025)
Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095.
0