CVE-2025-1053: Brocade SANnav encryption key is logged in the debug logs
First published: Fri Feb 14 2025(Updated: )
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.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-1053?
CVE-2025-1053 has been assigned a high severity rating due to the risk of privileged access to sensitive encryption keys.
How do I fix CVE-2025-1053?
To fix CVE-2025-1053, ensure that your Brocade SANnav installation is updated to the latest version that addresses the vulnerability.
Who is affected by CVE-2025-1053?
CVE-2025-1053 affects users of Brocade SANnav who install or upgrade the software under specific error conditions.
What kind of access is required to exploit CVE-2025-1053?
Exploitation of CVE-2025-1053 requires an attacker to have privileged access to the Brocade SANnav database.
What could an attacker do with the information from CVE-2025-1053?
An attacker leveraging CVE-2025-1053 could use the compromised encryption key to retrieve passwords stored in the Brocade SANnav database.
- agent/title
- agent/weakness
- agent/references
- agent/description
- agent/first-publish-date
- agent/type
- collector/nvd-api
- source/NVD
- agent/event
- agent/severity
- agent/source
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/brocade
- canonical/broadcom sannav ova