User impersonation via credential logging
Published Jan 3, 2024 · Updated Jun 3, 2025
Sensitive-data exposure in CubeFS before 3.3.1 allows local users to obtain access and secret keys from user-creation logs. The createKey function in master/user.go passes the new user's identifier, access key, and secret key to log.LogInfof without redaction. Access to master logs and a user-creation event is required; exposed credentials allow impersonation of the corresponding user.
Summary
What happened
Sensitive-data exposure in CubeFS before 3.3.1 allows local users to obtain access and secret keys from user-creation logs. The createKey function in master/user.go passes the new user's identifier, access key, and secret key to log.LogInfof without redaction. Access to master logs and a user-creation event is required; exposed credentials allow impersonation of the corresponding user.
The record
- CVE
- CVE-2023-46742
- Published
- Jan 3, 2024
- Updated
- Jun 3, 2025
- Vendor
- CubeFS
- Product
- CubeFS
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record 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=< 3.3.1
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