eosphoros-ai db-gpt up to 0.6.0 Web API /api/v1/editor/sql/run sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in eosphoros-ai db-gpt up to 0.6.0. Affected is an unknown function of the file /api/v1/editor/sql/run of the component Web API. Performing a manipulation results in sql injection. This vulnerability is cataloged as CVE-2024-10835. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in eosphoros-ai db-gpt up to 0.6.0. This affects an unknown functionality of the file /api/v1/editor/sql/run of the component Web API. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /api/v1/editor/sql/run` allows execution of arbitrary SQL queries without any access control. This vulnerability can be exploited by attackers to perform Arbitrary File Write using DuckDB SQL, enabling them to write arbitrary files to the victim's file system. This can potentially lead to Remote Code Execution (RCE).

The advisory is shared at huntr.com. This vulnerability is uniquely identified as CVE-2024-10835 since 11/05/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/18/2025). MITRE ATT&CK project uses the attack technique T1505 for this issue.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion