# CVE-2024-45855: MindsDB Deserialization of Untrusted Data vulnerability

> Attackers can execute arbitrary code on MindsDB servers by uploading a malicious model and triggering finetuning.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2024
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-fr9q-rgwq-g5r5, PYSEC-2024-85

## What is CVE-2024-45855?

CVE-2024-45855 is a high-severity unsafe deserialization vulnerability in mindsdb, published on 12 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Deserialization of untrusted data can occur in versions 23.10.2.0 and newer of the MindsDB platform, enabling a maliciously uploaded ‘inhouse’ model to run arbitrary code on the server when using ‘finetune’ on it.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mindsdb` | PyPI | From 23.10.2.0 | None |
| `mindsdb` | PyPI | From 23.10.2.0 to 24.9.2.1 | None |
| `mindsdb` | PyPI | From 23.10.2.0 to 24.9.2.1 | None |

Products: Mindsdb Mindsdb.

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

No fix has been published for CVE-2024-45855 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45855 being exploited?

There is no known exploitation of CVE-2024-45855 in the wild and no public exploit code.

## 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-45855 and fix it if it is affected.

What it is: CVE-2024-45855 is a high-severity unsafe deserialization vulnerability in mindsdb, published on 12 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45855 in the wild and no public exploit code.

Affected packages and fixed versions:
- mindsdb (PyPI): affected from 23.10.2.0; no fix listed
- mindsdb (PyPI): affected from 23.10.2.0 up to 24.9.2.1; no fix listed
- mindsdb (PyPI): affected from 23.10.2.0 up to 24.9.2.1; no fix listed

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

## Sources

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

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