# CVE-2024-45846: MindsDB Eval Injection vulnerability

> Attackers can execute arbitrary Python code on MindsDB servers via crafted SQL queries when the Weaviate integration is enabled.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Sep 2024
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-wcjw-3v6p-4v3r, PYSEC-2024-77

## What is CVE-2024-45846?

CVE-2024-45846 is a high-severity code injection vulnerability in mindsdb, published on 12 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An arbitrary code execution vulnerability exists in versions 23.10.3.0 up to 24.7.4.1 of the MindsDB platform, when the Weaviate integration is installed on the server. If a specially crafted ‘SELECT WHERE’ clause containing Python code is run against a database created with the Weaviate engine, the code will be passed to an eval function and executed on the server.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2024-45846?

3 open source packages ship an affected version, including mindsdb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mindsdb` | PyPI | From 23.10.3.0 | 24.7.4.1 |
| `mindsdb` | PyPI | From 23.10.3.0 | 24.7.4.1 |
| `mindsdb` | PyPI | From 23.10.3.0 | 24.7.4.1 |

Products: Mindsdb Mindsdb.

## How do I fix CVE-2024-45846?

Upgrade mindsdb to 24.7.4.1 or later.

## Is CVE-2024-45846 being exploited?

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

Public exploit code:

- Case study: MindsDB CVE-2024-45846..45851 (builtin eval on query values in integration handlers). Demo only, not for use. (github_poc): https://github.com/ferralon-demo/mindsdb-vectordb-eval-rce

## Other vulnerabilities in mindsdb

- [CVE-2024-24759](https://insights.sbomify.com/CVE-2024-24759/): MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding (critical 9.3)
- [CVE-2023-50731](https://insights.sbomify.com/CVE-2023-50731/): MindsDB has arbitrary file write in file.py (critical 9.1)
- [CVE-2023-38699](https://insights.sbomify.com/CVE-2023-38699/): MindsDB 'Call to requests with verify=False disabling SSL certificate checks, security issue.' issue (critical 9.1)
- [CVE-2024-45856](https://insights.sbomify.com/CVE-2024-45856/): MindsDB Cross-site Scripting vulnerability (critical 9.0)
- [CVE-2026-27483](https://insights.sbomify.com/CVE-2026-27483/): MindsDB has Path Traversal in /api/files Leading to Remote Code Execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45846 and fix it if it is affected.

What it is: CVE-2024-45846 is a high-severity code injection vulnerability in mindsdb, published on 12 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45846 exists.

Affected packages and fixed versions:
- mindsdb (PyPI): affected from 23.10.3.0; fixed in 24.7.4.1
- mindsdb (PyPI): affected from 23.10.3.0; fixed in 24.7.4.1
- mindsdb (PyPI): affected from 23.10.3.0; fixed in 24.7.4.1

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-2024-45846/ (Markdown: https://insights.sbomify.com/CVE-2024-45846/index.md)
```

## Sources

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

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