CVE-2024-29957

Encryption key is stored in the DR log files

HIGH
7.5
CVSS Score
Published: April 19, 2024 at 03:11 AM UTC
Updated: June 17, 2026 at 07:23 AM UTC
2 products affected across 2 vendorsBrocade SANnavSANnav

Using Brocade SANnav by Brocade?

Get instant alerts when new vulnerabilities affect Brocade SANnav - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.3.0av < 2.3.1
Affected range stops below 2.3.0a, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement
v < 2.3.0a
Affected range stops below 2.3.0a, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHbrocade
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card