Authenticated log disclosure via debug logging
Published May 9, 2022 · Updated Aug 3, 2024
Information exposure in Brocade SANnav before 2.2.0 allows local users to read SSH passwords via debug-mode filetansfer.log. The debug logging path writes sensitive SSH credentials into filetansfer.log instead of protecting or redacting them. Valid SANnav credentials and debug mode are required, and the consequence is disclosure of logged secrets without demonstrated integrity or availability impact.
Summary
What happened
Information exposure in Brocade SANnav before 2.2.0 allows local users to read SSH passwords via debug-mode filetansfer.log. The debug logging path writes sensitive SSH credentials into filetansfer.log instead of protecting or redacting them. Valid SANnav credentials and debug mode are required, and the consequence is disclosure of logged secrets without demonstrated integrity or availability impact.
The record
- CVE
- CVE-2022-28161
- Published
- May 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Broadcom
- Product
- Brocade SANnav
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Brocade SANNav before 2.2.0
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