Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Go github.com/ydb-platform/ydb-go-sdk/v3 >= 3.104.6, <= 3.134.1
Fixed in
3.134.2· Vendor fix available
Issue
Impact Transactions were NOT committed despite the explicit options.WithCommit flag using table service client. Because of this, clients did not commit changes to the transaction, relying on the fact that the transaction commit was successful. This led (in rare cases) to a loss of data consistency. Patches ydb-go-sdk contains this problem in versions from v3.104.6 to v3.134.1. The fix for this problem has been released in version v3.134.2 (https://github.com/ydb-platform/ydb-go-sdk/pull/2091). Workarounds 1) Use explicit table.Transaction.CommitTx(ctx) instead use options.WithCommit(). 2) Use transaction retrier db.Table().DoTx(ctx, lambda) instead explicit start transaction on session. 3) Use query client db.Query().Do(ctx, lambda) with the same logic in lambda Resources Commit with bug https://github.com/ydb-platform/ydb-go-sdk/commit/251128a64763555d9a79ee7a131dd154c9000eb9 Commit with fix https://github.com/ydb-platform/ydb-go-sdk/commit/25dcff4c41153f1f9413512ba12999b40bf7154d
Recommended action: Upgrade to 3.134.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/ydb-platform/ydb-go-sdk/v3 >= 3.48.6, < 3.53.3
Fixed in
3.53.3· Vendor fix available
Issue
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) -…
Recommended action: Upgrade to 3.53.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.