Security Digest · Vulnerability record
CVE-2024-10831: DB-GPT Absolute Path Traversal vulnerability
In eosphoros-ai/db-gpt version 0.6.0, the endpoint for uploading files is vulnerable to absolute path traversal.
CVSS 9.1 Critical EPSS 0.8% · p57
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.8%, percentile 57: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 57% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
dbgpt(PyPI) <= 0.6.0, no fixed version listed. Check your lockfile, including transitive dependencies.
What it is
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 filekey and docfile.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.
From the GitHub advisory
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 filekey and docfile.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 type: CWE-36.
Product: dbgpt (PyPI) · Assigned by: @huntr_ai · Published: 2025-03-20
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | dbgpt | <= 0.6.0 | none listed |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| eosphoros-ai | eosphoros-ai/db-gpt | unspecified <= latest |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.1 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| GitHub | 3.1 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 0.84% probability of exploitation activity in the next 30 days; percentile 57.
Timeline
- — CVE record last updated
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-hhw5-29f6-hf4x published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-hhw5-29f6-hf4x github.com
- CVE.org record CVE-2024-10831 cve.org
- NVD entry CVE-2024-10831 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com