ydb-go-sdk token in custom credentials object can leak through logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2023-45825: 0.23% estimated exploitation activity in the next 30 days; percentile 14.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Printf func use placeholder %q for string representation of argument with quotes. If an argument implements interface fmt.Stringer, it will used through String() func. In other cases used fallback - serialization with reflection. 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. Who is impacted: applications with custom credentials object with an explicit token field. A leak could have occurred if all of these conditions were met simultaneously: 1) The credentials object does not implement the fmt.Stringer interface (does not have a String() method) -…

Published by the source

19 Oct 2023, 17:10 UTC

Last modified by the source

6 Dec 2023, 12:39 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q24m-6h38-5xj8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-45825

Advisory: ydb-go-sdk token in custom credentials object can leak through logs
IDs: CVE-2023-45825, GHSA-q24m-6h38-5xj8
Record: https://patchnext.com/advisories/cve-2023-45825 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ydb-platform/ydb-go-sdk/v3 3.53.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ydb-platform/ydb-go-sdk/v3: affected >= 3.48.6, < 3.53.3; fixed in 3.53.3

## Suggested inspection (read-only)
- Go github.com/ydb-platform/ydb-go-sdk/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ydb-platform/ydb-go-sdk/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q24m-6h38-5xj8 (GitHub-reviewed advisory GHSA-q24m-6h38-5xj8 lists affected ranges: Go github.com/ydb-platform/ydb-go-sdk/v3 >=3.48.6 <3.53.3)

Commands are suggestions: review each one before running it.