Menu

Star on GitHub · 3.2k

CVE-2025-1053

4.9 · MEDIUM

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.

Published Feb 14, 2025CWE-532EPSS 0.16%

Overview

CVE-2025-1053 is a medium-severity vulnerability. It was published on February 14, 2025 and has a CVSS 3.1 base score of 4.9 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 4.9, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-1053?

CVE-2025-1053 is a medium-severity vulnerability. It was published on February 14, 2025 and has a CVSS 3.1 base score of 4.9 (MEDIUM).

How severe is CVE-2025-1053?

This vulnerability has a CVSS 3.1 base score of 4.9, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-1053?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-1053?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-1053 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2025

View all