# CVE-2023-39662: llama-index vulnerable to arbitrary code execution

> Remote attackers can execute arbitrary code via the exec parameter in PandasQueryEngine, affecting users of the llama_index library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-2xxc-73fv-36f7, PYSEC-2023-148

## What is CVE-2023-39662?

CVE-2023-39662 is a critical code injection vulnerability in n/a, published on 15 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in llama_index v.0.7.13 and before allows a remote attacker to execute arbitrary code via the `exec` parameter in PandasQueryEngine function.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-39662?

3 open source packages ship an affected version, including llama-index. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `llama-index` | PyPI | All versions | 0.7.14 |
| `llama-index` | PyPI | All versions | 0.9.14 |
| `llama-index` | PyPI | All versions | 0.9.14 |

Products: Llamaindex Project Llamaindex.

## How do I fix CVE-2023-39662?

Upgrade llama-index to a fixed version for your release line: 0.7.14 or 0.9.14.

## Is CVE-2023-39662 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39662 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39662 and fix it if it is affected.

What it is: CVE-2023-39662 is a critical code injection vulnerability in n/a, published on 15 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39662 exists.

Affected packages and fixed versions:
- llama-index (PyPI): affected all versions; fixed in 0.7.14
- llama-index (PyPI): affected all versions; fixed in 0.9.14
- llama-index (PyPI): affected all versions; fixed in 0.9.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-39662/ (Markdown: https://insights.sbomify.com/CVE-2023-39662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39662
- OSV: https://osv.dev/vulnerability/CVE-2023-39662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-39662/
Summaries are generated and may contain mistakes; the official description above is the record.