LLAMA-INDEX-CORE · CVE-2024-45201 · AI agents & MCP
FIX → 0.10.38
LlamaIndex's integration download code passes a class name into an exec call, so a crafted name becomes Python code that runs. An attacker who can influence that name gets code execution in the process running LlamaIndex.
first public Aug 22, 2024 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that import the LlamaIndex integration download code (download/integration.py) with an affected llama-index-core version. The sources do not say which input reaches the class name, so whether a given app is reachable is unknown; teams that never load LlamaIndex integrations at runtime are less exposed.
Not affected if version-0.10.38-or-later
Who cares llama-index-core, llamaindex, python
pip show llama-index-core and compare the version with 0.10.38llama-index-core pinned below 0.10.38 in requirements or lock filesUpgrade to 0.10.38
An issue was discovered in llama_index before 0.10.38. download/integration.py includes an exec call for import {cls_name}.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
llama-index-core to 0.10.38 or laterGitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.