Code Injection in llama-index (CVE-2024-4181)
Summary
Code injection in llama-index (CVE-2024-4181). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.10.13 or later.
Original description
The description as published by the source.
A command injection vulnerability exists in the RunGptLLM class of the llama_index library, version 0.9.47, used by the RunGpt framework from JinaAI to connect to Language Learning Models (LLMs). The vulnerability arises from the improper use of the eval function, allowing a malicious or compromised LLM hosting provider to execute arbitrary commands on the client's machine. This issue was fixed in version 0.10.13. The exploitation of this vulnerability could lead to a hosting provider gaining full control over client machines.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-4181 has been found in llama-index.
Successful exploitation can lead to full system takeover.
What to do: upgrade llama-index to 0.10.13 or later.
If unsure, ask your IT team or search "llama-index CVE-2024-4181" on the vendor's site.
CVE-2024-4181 (llama-index) — CWE-94
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.10.13 — 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.
Arbitrary code execution (CWE-94) exists in llama-index.
Check the vendor advisory for the affected versions of llama-index.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.10.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'llama-index' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'llama-index' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
llama-indexを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade llama-index to 0.10.13ステージング環境で 0.10.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web huntr.com