# CVE-2023-50731: MindsDB has arbitrary file write in file.py

> Attackers can write arbitrary files or delete specific archives on the server via path traversal in the file upload API, potentially compromising system integrity.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 22 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-j8w6-2r9h-cxhj, PYSEC-2023-279

## What is CVE-2023-50731?

CVE-2023-50731 is a critical path traversal vulnerability in mindsdb, published on 22 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MindsDB is a SQL Server for artificial intelligence. Prior to version 23.11.4.1, the `put` method in `mindsdb/mindsdb/api/http/namespaces/file.py` does not validate the user-controlled name value, which is used in a temporary file name, which is afterwards opened for writing on lines 122-125, which leads to path injection. Later in the method, the temporary directory is deleted on line 151, but since we can write outside of the directory using the path injection vulnerability, the potentially dangerous file is not deleted. Arbitrary file contents can be written due to `f.write(chunk)` on line 125. Mindsdb does check later on line 149 in the `save_file` method in `file-controller.py` which calls the `_handle_source` method in `file_handler.py` if a file is of one of the types `csv`, `json`, `parquet`, `xls`, or `xlsx`. However, since the check happens after the file has already been written, the files will still exist (and will not be removed due to the path injection described earlier), just the `_handle_source` method will return an error. The same user-controlled source source is used also in another path injection sink on line 138. This leads to another path injection, which allows an attacker to delete any `zip` or `tar.gz` files on the server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mindsdb` | PyPI | All versions | 23.11.4.1 |
| `mindsdb` | PyPI | All versions | 23.11.4.1 |
| `mindsdb` | PyPI | All versions | 23.11.4.1 |

Products: Mindsdb Mindsdb.

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

Upgrade mindsdb to 23.11.4.1 or later.

## Is CVE-2023-50731 being exploited?

There is no known exploitation of CVE-2023-50731 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-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)
- [CVE-2024-45846](https://insights.sbomify.com/CVE-2024-45846/): MindsDB Eval Injection vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50731 is a critical path traversal vulnerability in mindsdb, published on 22 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50731 in the wild and no public exploit code.

Affected packages and fixed versions:
- mindsdb (PyPI): affected all versions; fixed in 23.11.4.1
- mindsdb (PyPI): affected all versions; fixed in 23.11.4.1
- mindsdb (PyPI): affected all versions; fixed in 23.11.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-2023-50731/ (Markdown: https://insights.sbomify.com/CVE-2023-50731/index.md)
```

## Sources

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

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