eosphoros-ai db-gpt up to up to 0.6.0 doc_file.filename path traversal

Summaryinfo

A vulnerability labeled as critical has been found in eosphoros-ai db-gpt up to up to 0.6.0. This affects an unknown part. The manipulation of the argument doc_file.filename results in path traversal. This vulnerability is cataloged as CVE-2024-10833. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in eosphoros-ai db-gpt up to up to 0.6.0. Affected is an unknown part. The manipulation of the argument doc_file.filename with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on integrity, and availability. CVE summarizes:

eosphoros-ai/db-gpt version 0.6.0 is vulnerable to an arbitrary file write through the knowledge API. The endpoint for uploading files as 'knowledge' is susceptible to absolute path traversal, allowing attackers to write files to arbitrary locations on the target server. This vulnerability arises because the 'doc_file.filename' parameter is user-controllable, enabling the construction of absolute paths.

The advisory is shared for download at huntr.com. This vulnerability is traded as CVE-2024-10833 since 11/05/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/17/2025). The MITRE ATT&CK project declares the attack technique as T1006.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• eosphoros-ai

Name

• db-gpt

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion