# CVE-2024-10831: Arbitrary File Write through Absolute Path Traversal in eosphoros-ai/db-gpt

> Attackers can upload arbitrary files to any location on the server via path traversal, potentially overwriting system files to achieve code execution.

- **Severity:** Critical 9.1 (`CVSS:3.0/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:** No
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-hhw5-29f6-hf4x, PYSEC-2026-323

## What is CVE-2024-10831?

CVE-2024-10831 is a critical path traversal vulnerability in eosphoros-ai/db-gpt, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In eosphoros-ai/db-gpt version 0.6.0, the endpoint for uploading files is vulnerable to absolute path traversal. This vulnerability allows an attacker to upload arbitrary files to arbitrary locations on the target server. The issue arises because the `file_key` and `doc_file.filename` parameters are user-controllable, enabling the construction of paths outside the intended directory. This can lead to overwriting essential system files, such as SSH keys, for further exploitation.

Weakness: CWE-36 (Absolute Path Traversal)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |
| `dbgpt` | PyPI | All versions to 0.6.0 | None |

Products: Dbgpt Db-Gpt.

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

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

## Is CVE-2024-10831 being exploited?

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

## Other vulnerabilities in eosphoros-ai/db-gpt

- [CVE-2024-10833](https://insights.sbomify.com/CVE-2024-10833/): Arbitrary File Write in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10834](https://insights.sbomify.com/CVE-2024-10834/): Arbitrary File Write in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10835](https://insights.sbomify.com/CVE-2024-10835/): Arbitrary File Write via SQL Injection in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10901](https://insights.sbomify.com/CVE-2024-10901/): Arbitrary File Write via DuckDB SQL Injection in eosphoros-ai/db-gpt (critical 9.1)
- [CVE-2024-10902](https://insights.sbomify.com/CVE-2024-10902/): Arbitrary File Upload with Path Traversal in eosphoros-ai/db-gpt (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10831 is a critical path traversal vulnerability in eosphoros-ai/db-gpt, published on 20 Mar 2025. 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-2024-10831 exists.

Affected packages and fixed versions:
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed
- dbgpt (PyPI): affected all versions up to 0.6.0; no fix listed
- dbgpt (PyPI): affected all versions up to 0.6.0; 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-10831/ (Markdown: https://insights.sbomify.com/CVE-2024-10831/index.md)
```

## Sources

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

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