SCP credential disclosure via Base64 log storage
Published Jun 27, 2022 · Updated Aug 3, 2024
Insecure credential storage in Broadcom Brocade SANnav before 2.2.0.2 and 2.1.1.8 allows local users to read SCP-server passwords. The encryption component writes SCP-server passwords into log files using reversible Base64 encoding rather than protecting the credential material. Access to the SANnav host and permission to read the affected logs are required; decoding exposes credentials that can authenticate to configured SCP servers.
Summary
What happened
Insecure credential storage in Broadcom Brocade SANnav before 2.2.0.2 and 2.1.1.8 allows local users to read SCP-server passwords. The encryption component writes SCP-server passwords into log files using reversible Base64 encoding rather than protecting the credential material. Access to the SANnav host and permission to read the affected logs are required; decoding exposes credentials that can authenticate to configured SCP servers.
The record
- CVE
- CVE-2022-28168
- Published
- Jun 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Broadcom
- Product
- Brocade SANnav
- Classifications
- CWE-922, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 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=versions before v2.2.0.2 and v2.1.1.8
What conditions does exploitation require?
What is affected?
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