Ydb Go Sdk
Approved changes feed: RSS · Atom
cpe:2.3:a:ydb-platform:ydb-go-sdk:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Ydb Platform (8a221a8c-464f-5cc9-8ab3-73f79f04fd75) |
|---|---|
| Product | Ydb Go Sdk (aba5c2de-a993-520c-8df1-ae919e6c67c7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-45825 |
vulnerable | 2026-06-08 06:12:43.414507 |
Token in custom credentials object can leak through logs in ydb-go-sdk
MEDIUM (5.5)
ydb-go-sdk is a pure Go native and database/sql driver for the YDB platform. Since ydb-go-sdk v3.48.6 if you use a custom credentials object (implementation of interface Credentials it may leak into logs. This happens because this object could be serialized into an error message using `fmt.Errorf("something went wrong (credentials: %q)", credentials)` during connection to the YDB server. If such logging occurred, a malicious user with access to logs could read sensitive information (i.e. credentials) information and use it to get access to the database. ydb-go-sdk contains this problem in versions from v3.48.6 to v3.53.2. The fix for this problem has been released in version v3.53.3. Users are advised to upgrade. Users unable to upgrade should implement the `fmt.Stringer` interface in your custom credentials type with explicit stringify of object state.
Published: 2023-10-19T18:22:31.034Z
Updated: 2024-09-12T17:52:08.400Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.