Vulnerability in llama-index-core (CVE-2024-12704)
Summary
Vulnerability in llama-index-core (CVE-2024-12704). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.12.6 or later.
Original description
The description as published by the source.
A vulnerability in the LangChainLLM class of the run-llama/llama_index repository, version v0.12.5, allows for a Denial of Service (DoS) attack. The stream_complete method executes the llm using a thread and retrieves the result via the get_response_gen method of the StreamingGeneratorCallbackHandler class. If the thread terminates abnormally before the _llm.predict is executed, there is no exception handling for this case, leading to an infinite loop in the get_response_gen function. This can be triggered by providing an input of an incorrect type, causing the thread to terminate and the process to continue running indefinitely.
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-12704 has been found in llama-index-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade llama-index-core to 0.12.6 or later.
If unsure, ask your IT team or search "llama-index-core CVE-2024-12704" on the vendor's site.
CVE-2024-12704 (llama-index-core) — CWE-755
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.12.6 — 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.
A vulnerability (CWE-755) exists in llama-index-core.
Check the vendor advisory for the affected versions of llama-index-core.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.12.6.
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-core' . 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-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
llama-index-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade llama-index-core to 0.12.6ステージング環境で 0.12.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web huntr.com