Encryption-key disclosure via Disaster Recovery logging
Published Apr 19, 2024 · Updated Aug 2, 2024
Sensitive-data exposure in Brocade SANnav before 2.3.0a allows remote attackers to obtain an encryption key from DR logs. The DRMODE component writes the encryption key into Disaster Recovery log files, creating a less-protected copy of the secret. Exposure requires Disaster Recovery mode and access to its logs; acquisition of the key compromises protected-data confidentiality.
Summary
What happened
Sensitive-data exposure in Brocade SANnav before 2.3.0a allows remote attackers to obtain an encryption key from DR logs. The DRMODE component writes the encryption key into Disaster Recovery log files, creating a less-protected copy of the secret. Exposure requires Disaster Recovery mode and access to its logs; acquisition of the key compromises protected-data confidentiality.
The record
- CVE
- CVE-2024-29957
- Published
- Apr 19, 2024
- Updated
- Aug 2, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- CWE-532, CAPEC-37, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.3.0a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo