← Back
GHSA-28xx-pppm-vqff
Vulnerability in github.com/ydb-platform/ydb-go-sdk/v3 (GHSA-28xx-pppm-vqff)
Summary
vulnerability in github.com/ydb-platform/ydb-go-sdk/v3 (GHSA-28xx-pppm-vqff). Risk of unauthorized operations or information disclosure. Exploitable via ``options.WithCommit``. Mitigation: upgrade to `3.134.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-28xx-pppm-vqff** has been found in github.com/ydb-platform/ydb-go-sdk/v3.
Attackers can target a specific entry point like ``options.WithCommit`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/ydb-platform/ydb-go-sdk/v3 to **3.134.2** or later.
If unsure, ask your IT team or search "github.com/ydb-platform/ydb-go-sdk/v3 GHSA-28xx-pppm-vqff" on the vendor's site.
GHSA-28xx-pppm-vqff (github.com/ydb-platform/ydb-go-sdk/v3) — CWE-670 /
Attack surface: `options.WithCommit` / `lambda`
Patched: `3.134.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-670) exists in github.com/ydb-platform/ydb-go-sdk/v3. Attackers reach the vulnerable code path via ``options.WithCommit`` without authentication.
📍 Affected scope
github.com/ydb-platform/ydb-go-sdk/v3 — . Attack surface: `options.WithCommit` / `lambda`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.134.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/ydb-platform/ydb-go-sdk/v3' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/ydb-platform/ydb-go-sdk/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/ydb-platform/ydb-go-sdk/v3` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/ydb-platform/ydb-go-sdk/v3 to 3.134.2ステージング環境で 3.134.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/ydb-platform/ydb-go-sdk/v3
[{"type":"SEMVER","events":[{"introduced":"3.104.6"},{"fixed":"3.134.2"}]}]
References
- package https://github.com/ydb-platform/ydb-go-sdk
- web https://github.com/ydb-platform/ydb-go-sdk/security/advisories/GHSA-28xx-pppm-vqff
- web https://github.com/ydb-platform/ydb-go-sdk/commit/251128a64763555d9a79ee7a131dd154c9000eb9
- web https://github.com/ydb-platform/ydb-go-sdk/commit/25dcff4c41153f1f9413512ba12999b40bf7154d
- web https://github.com/ydb-platform/ydb-go-sdk/pull/2091
- web https://github.com/ydb-platform/ydb-go-sdk/releases/tag/v3.104.6
- web https://github.com/ydb-platform/ydb-go-sdk/releases/tag/v3.134.1
- web https://github.com/ydb-platform/ydb-go-sdk/releases/tag/v3.134.2