# 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.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **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 available:** No
- **Published:** 14 Feb 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-jx64-r67p-6v8c

## 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 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-1053?

It affects 1 product.


Products: 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](https://insights.sbomify.com/CVE-2019-16211/): Hardcoded credentials in Brocade SANnav (critical 9.8)
- [CVE-2024-3596](https://insights.sbomify.com/CVE-2024-3596/): RADIUS Protocol under RFC2865 is vulnerable to forgery attacks. (critical 9.0)
- [CVE-2019-16212](https://insights.sbomify.com/CVE-2019-16212/): A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. (high 8.8)
- [CVE-2019-16205](https://insights.sbomify.com/CVE-2019-16205/): Weak cryptography in Brocade SANnav (high 8.8)
- [CVE-2024-2240](https://insights.sbomify.com/CVE-2024-2240/): Docker implementation in Brocade SANnav is missing Audit Rules. (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1053 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-1053 in the wild and no public exploit code.

Affected product: Broadcom Brocade Sannav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1053/ (Markdown: https://insights.sbomify.com/CVE-2025-1053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1053
- OSV: https://osv.dev/vulnerability/CVE-2025-1053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1053/
Summaries are generated and may contain mistakes; the official description above is the record.