Credential disclosure via supportsave secret logging
Published Nov 21, 2024 · Updated Nov 21, 2024
Information exposure in Brocade SANnav before 2.2.2 allows local users with administrator access to read configuration secrets. The supportsave collection process writes configuration values, including usernames, passwords, and secret keys, into its generated troubleshooting archive without redacting them. Exploitation requires an administrator to generate the supportsave file, after which access to the archive exposes the recorded credentials and keys.
Summary
What happened
Information exposure in Brocade SANnav before 2.2.2 allows local users with administrator access to read configuration secrets. The supportsave collection process writes configuration values, including usernames, passwords, and secret keys, into its generated troubleshooting archive without redacting them. Exploitation requires an administrator to generate the supportsave file, after which access to the archive exposes the recorded credentials and keys.
The record
- CVE
- CVE-2022-43933
- Published
- Nov 21, 2024
- Updated
- Nov 21, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- CWE-538, CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 21, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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=before Brocade SANnav 2.2.2
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