← Back
CVE-2024-11958
SQL Injection in llama-index-retrievers-duckdb-retriever (CVE-2024-11958)
Summary
SQL injection in llama-index-retrievers-duckdb-retriever (CVE-2024-11958). Successful exploitation can lead to full system takeover. Exploitable via ``duckdb_retriever``. Mitigation: upgrade to `0.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-11958** has been found in llama-index-retrievers-duckdb-retriever.
Attackers can target a specific entry point like ``duckdb_retriever`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade llama-index-retrievers-duckdb-retriever to **0.4.0** or later.
If unsure, ask your IT team or search "llama-index-retrievers-duckdb-retriever CVE-2024-11958" on the vendor's site.
CVE-2024-11958 (llama-index-retrievers-duckdb-retriever) — CWE-89 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `duckdb_retriever`
Patched: `0.4.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
**SQL injection** (CWE-89) exists in llama-index-retrievers-duckdb-retriever. Attackers reach the vulnerable code path via ``duckdb_retriever`` without authentication.
📍 Affected scope
llama-index-retrievers-duckdb-retriever — . Attack surface: `duckdb_retriever`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.4.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 'llama-index-retrievers-duckdb-retriever' .` 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 'llama-index-retrievers-duckdb-retriever' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `llama-index-retrievers-duckdb-retriever` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade llama-index-retrievers-duckdb-retriever to 0.4.0ステージング環境で 0.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
llama-index-retrievers-duckdb-retriever
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.0"}]}]
PyPI
llama-index-retrievers-duckdb-retriever
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-11958
- advisory https://github.com/advisories/GHSA-339r-cjv9-x78g
- package https://github.com/run-llama/llama_index
- package https://pypi.org/project/llama-index-retrievers-duckdb-retriever
- web https://github.com/run-llama/llama_index/commit/35bd221e948e40458052d30c6ef2779bc965b6d0
- web https://huntr.com/bounties/8ddf66e1-f74c-4d53-992b-76bc45cacac1
- web https://github.com/pypa/advisory-database/tree/main/vulns/llama-index-retrievers-duckdb-retriever/PYSEC-2026-399.yaml