Remote code execution via permissive safe_eval built-ins
Published Apr 16, 2024 · Updated Aug 1, 2024
Command injection in LlamaIndex before 0.10.24 allows remote attackers to execute arbitrary code through generated expressions. The safe_eval function evaluates generated Python after an AST check that blocks private or dunder names but leaves dangerous built-ins such as getattr available. Exploitation requires an application to pass attacker-influenced or model-generated code into safe_eval; successful input runs with the hosting process's permissions.
Summary
What happened
Command injection in LlamaIndex before 0.10.24 allows remote attackers to execute arbitrary code through generated expressions. The safe_eval function evaluates generated Python after an AST check that blocks private or dunder names but leaves dangerous built-ins such as getattr available. Exploitation requires an application to pass attacker-influenced or model-generated code into safe_eval; successful input runs with the hosting process's permissions.
The record
- CVE
- CVE-2024-3271
- Published
- Apr 16, 2024
- Updated
- Aug 1, 2024
- Vendor
- Run Llama
- Product
- LlamaIndex
- Classifications
- CWE-77, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=*
- Affected versionversion=unspecified <10.26
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr safe_eval bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo