← Back
GHSA-7rx4-c5vx-g8w3
SSRF (Server-Side Request Forgery) in @karakeep/sdk (GHSA-7rx4-c5vx-g8w3)
Summary
SSRF in @karakeep/sdk (GHSA-7rx4-c5vx-g8w3). Risk of unauthorized operations or information disclosure. Exploitable via ``href``. Mitigation: upgrade to `0.32.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-7rx4-c5vx-g8w3** has been found in @karakeep/sdk.
Attackers can target a specific entry point like ``href`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @karakeep/sdk to **0.32.0** or later.
If unsure, ask your IT team or search "@karakeep/sdk GHSA-7rx4-c5vx-g8w3" on the vendor's site.
GHSA-7rx4-c5vx-g8w3 (@karakeep/sdk) — CWE-918 /
Attack surface: `href` / `got`
Patched: `0.32.0` — 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
**SSRF** (CWE-918) exists in @karakeep/sdk. Attackers reach the vulnerable code path via ``href`` without authentication.
📍 Affected scope
@karakeep/sdk — . Attack surface: `href` / `got`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.32.0**.
🛡️ 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 '@karakeep/sdk' .` 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 '@karakeep/sdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@karakeep/sdk` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @karakeep/sdk to 0.32.0ステージング環境で 0.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@karakeep/sdk
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.32.0"}]}]
References
- package https://github.com/karakeep-app/karakeep
- web https://github.com/karakeep-app/karakeep/security/advisories/GHSA-7rx4-c5vx-g8w3
- web https://github.com/karakeep-app/karakeep/pull/2763
- web https://github.com/karakeep-app/karakeep/commit/3dc321e7d49aa3a1a2493637fb2ee21616fe5fd9
- web https://github.com/karakeep-app/karakeep/releases/tag/v0.32.0
- web https://github.com/advisories/GHSA-7rx4-c5vx-g8w3