CVE-2024-29957 Encryption key is stored in the DR log files
Attackers can read encryption keys from log files when Disaster Recovery mode is enabled, potentially compromising data confidentiality.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-29957?
CVE-2024-29957 is a high-severity vulnerability in Broadcom Brocade Sannav, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-532
Which versions are affected by CVE-2024-29957?
It affects 1 product.
Products include Broadcom Brocade Sannav.
How do I fix CVE-2024-29957?
No fix has been published for CVE-2024-29957 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-29957 being exploited?
There is no known exploitation of CVE-2024-29957 in the wild and no public exploit code.
Other vulnerabilities in Broadcom Brocade Sannav
- CVE-2019-16211 Hardcoded credentials in Brocade SANnav
- CVE-2024-3596 RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.
- CVE-2019-16212 A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection.
- CVE-2019-16205 Weak cryptography in Brocade SANnav
- CVE-2024-2240 Docker implementation in Brocade SANnav is missing Audit Rules.
Sources
Also known as GHSA-jw6c-wq8m-h8g9.