Credential disclosure via error-message serialization
Published Oct 19, 2023 · Updated Sep 12, 2024
Sensitive data exposure in YDB Go SDK 3.48.6 through 3.53.2 allows local users to read custom credentials from logged connection errors. The balancer formats a custom Credentials object with %q in an error returned by ydb.Open, triggering reflection-based serialization when fmt.Stringer is absent. Exposure requires a connection failure, a token-bearing custom credentials object without String(), configured application logging, and access to the resulting log.
Summary
What happened
Sensitive data exposure in YDB Go SDK 3.48.6 through 3.53.2 allows local users to read custom credentials from logged connection errors. The balancer formats a custom Credentials object with %q in an error returned by ydb.Open, triggering reflection-based serialization when fmt.Stringer is absent. Exposure requires a connection failure, a token-bearing custom credentials object without String(), configured application logging, and access to the resulting log.
The record
- CVE
- CVE-2023-45825
- Published
- Oct 19, 2023
- Updated
- Sep 12, 2024
- Vendor
- YDB
- Product
- YDB Go SDK
- Classifications
- CWE-532, CAPEC-215, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 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=>= 3.48.6, < 3.53.3
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