How severe is CVE-2024-29957?

CVE-2024-29957 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2024-29957 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-29957?

CVE-2024-29957 affects Broadcom Brocade Sannav. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-29957?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-29957 have an EU (EUVD) identifier?

Yes. CVE-2024-29957 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-26931.

When was CVE-2024-29957 published?

CVE-2024-29957 was published on 2024-04-19 and last updated on 2026-06-17.

CVE-2024-29957

CVE-2024-29957 is a high-severity vulnerability in Broadcom Brocade Sannav with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (22nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-26931
Weakness: CWE-532
Affected product: Broadcom Brocade Sannav
Published: 2024-04-19
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2024-29957?: 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.
How severe is CVE-2024-29957?: CVE-2024-29957 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2024-29957 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-29957?: CVE-2024-29957 affects Broadcom Brocade Sannav. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-29957?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-29957 have an EU (EUVD) identifier?: Yes. CVE-2024-29957 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-26931.
When was CVE-2024-29957 published?: CVE-2024-29957 was published on 2024-04-19 and last updated on 2026-06-17.

References

https://support.broadcom.com/external/content/SecurityAdvisories/0/23241

Affected products (1)

cpe:2.3:a:broadcom:brocade_sannav:*:*:*:*:*:*:*:*

More vulnerabilities in Broadcom Brocade Sannav

CVE-2024-4282 — Critical (CVSS 9.8): Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.
CVE-2022-23305 — Critical (CVSS 9.8): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be…
CVE-2019-16211 — Critical (CVSS 9.8): Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability.
CVE-2024-3596 — Critical (CVSS 9.0): RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response…
CVE-2022-23302 — High (CVSS 8.8): JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write…
CVE-2019-16212 — High (CVSS 8.8): A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP…

All CVEs affecting Broadcom Brocade Sannav →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →