REST API token disclosure via plaintext logging
Published May 9, 2022 · Updated Aug 3, 2024
Cleartext credential storage in Broadcom Brocade SANnav before 2.2.0 allows local users to read REST API authentication tokens from logs. SANnav writes REST API authentication tokens directly to a log in plain text instead of excluding or protecting those credentials. A user with low-privileged local access can read a token and obtain the authenticated API session it represents.
Summary
What happened
Cleartext credential storage in Broadcom Brocade SANnav before 2.2.0 allows local users to read REST API authentication tokens from logs. SANnav writes REST API authentication tokens directly to a log in plain text instead of excluding or protecting those credentials. A user with low-privileged local access can read a token and obtain the authenticated API session it represents.
The record
- CVE
- CVE-2022-28162
- Published
- May 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Broadcom
- Product
- Brocade SANnav
- Classifications
- CWE-312, 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?
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