← Back
CVE-2024-52294
Vulnerability in khoj (CVE-2024-52294)
Summary
vulnerability in khoj (CVE-2024-52294). Risk of unauthorized operations or information disclosure. Exploitable via `PATCH /api/subscription`. Mitigation: upgrade to `1.29.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-52294** has been found in khoj.
Attackers can target a specific entry point like `PATCH /api/subscription` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade khoj to **1.29.0** or later.
If unsure, ask your IT team or search "khoj CVE-2024-52294" on the vendor's site.
CVE-2024-52294 (khoj) — CWE-639 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/subscription
Patched: `1.29.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
**A vulnerability** (CWE-639) exists in khoj. Attackers reach the vulnerable code path via `PATCH /api/subscription` without authentication.
📍 Affected scope
khoj — . Attack surface: PATCH /api/subscription.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.29.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 `PATCH /api/subscription` requests with malformed payloads or SQL meta-characters. Run `grep -r 'khoj' .` 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 'khoj' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `khoj` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'PATCH /api/subscription' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `PATCH /api/subscription` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade khoj to 1.29.0ステージング環境で 1.29.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against PATCH /api/subscription on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
khoj
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.29.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-52294
- advisory https://github.com/advisories/GHSA-hq4h-w933-jm6c
- package https://github.com/khoj-ai/khoj
- package https://pypi.org/project/khoj
- web https://github.com/khoj-ai/khoj/security/advisories/GHSA-hq4h-w933-jm6c
- web https://github.com/khoj-ai/khoj/commit/47d3c8c23597900af708bdc60aced3ae5d2064c1