CVE-2025-1053 Brocade SANnav encryption key is logged in the debug logs
An attacker with privileged database access can retrieve encryption keys from debug logs to decrypt stored passwords in Brocade SANnav.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2025-1053?
CVE-2025-1053 is a high-severity vulnerability in Broadcom Brocade Sannav, published on 14 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-532
Which versions are affected by CVE-2025-1053?
It affects 1 product.
Products include Broadcom Brocade Sannav.
How do I fix CVE-2025-1053?
No fix has been published for CVE-2025-1053 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-1053 being exploited?
There is no known exploitation of CVE-2025-1053 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-jx64-r67p-6v8c.