Live › vulnerability › CVE-2024-10831
Go to dashboardDB-GPT, an AI database assistant, has an upload endpoint that builds file paths from user-supplied `file_key` and `doc_file.filename` values. An attacker can write arbitrary files to any location on the server, such as overwriting SSH keys or other system files.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 16:25 UTC, 0h before NVD. All times on this page are UTC.
Teams running DB-GPT 0.6.0 or earlier with the file upload endpoint reachable by users or the network. Deployments where that endpoint is not exposed or the service is not installed can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| dbgpt | pypi | <= 0.6.0 | – |
| dbgpt db-gpt | vendor | = 0.6.0 | – |
pip show dbgpt; versions up to and including 0.6.0 are affected.dbgpt to a version newer than 0.6.0; the sources do not name the fixed version, so check the GHSA advisory.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2024-10831")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.