run-llama llama_index up to 0.2.x database_agent run_sql_query sql injection

Summaryinfo

A vulnerability has been found in run-llama llama_index up to 0.2.x and classified as critical. Affected is the function run_sql_query of the component database_agent. The manipulation leads to sql injection. This vulnerability is listed as CVE-2024-12909. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, has been found in run-llama llama_index up to 0.2.x. This issue affects the function run_sql_query of the component database_agent. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A vulnerability in the FinanceChatLlamaPack of the run-llama/llama_index repository, versions up to v0.12.3, allows for SQL injection in the `run_sql_query` function of the `database_agent`. This vulnerability can be exploited by an attacker to inject arbitrary SQL queries, leading to remote code execution (RCE) through the use of PostgreSQL's large object functionality. The issue is fixed in version 0.3.0.

The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2024-12909 since 12/23/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 0.3.0 eliminates this vulnerability. Applying the patch 5d03c175476452db9b8abcdb7d5767dd7b310a75 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• run-llama

Name

• llama_index

Version

• 0.1
• 0.2

License

• open-source

Website

• Product: https://github.com/run-llama/llama_index/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion