LlamaIndex Retrievers Integration: DuckDBRetriever SQL Injection

The impact of this SQL injection vulnerability is severe. An attacker can leverage it to execute arbitrary SQL commands against the DuckDB database. The description explicitly mentions the possibility of achieving remote code execution (RCE) by installing the shellfs extension and then executing malicious commands. This could allow an attacker to gain complete control over the affected system, exfiltrate sensitive data, modify database contents, or even pivot to other systems within the network. The potential for data breaches and system compromise is significant.

Applications leveraging the llama-index-retrievers-duckdb-retriever component for data retrieval from DuckDB databases are at risk. This includes projects utilizing the run-llama/llama_index repository and those integrating DuckDB as a data source. Specifically, deployments using older versions (≤0.3.0) and those lacking robust input validation are particularly vulnerable.

• python / supply-chain:

import subprocess
result = subprocess.run(['pip', 'show', 'llama-index-retrievers-duckdb-retriever'], capture_output=True, text=True)
if 'Version: 0.3.0' in result.stdout:
    print('Vulnerable version detected!')

• generic web: Check for DuckDB database endpoints exposed in the application. Use curl to test for SQL injection vulnerabilities.

curl 'http://example.com/duckdb_endpoint?query=1%20OR%201=1' # Replace with actual endpoint

1. 2025-03-20Disclosure

   disclosure

1. Réservé2024-11-28
2. Publiée2025-03-20
3. Modifiée2025-05-28
4. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2024-11958 is to upgrade the llama-index-retrievers-duckdb-retriever component to version 0.4.0 or later. If an immediate upgrade is not feasible due to compatibility issues or breaking changes, consider implementing stricter input validation on any user-supplied data used in SQL queries. While not a complete solution, this can reduce the attack surface. Additionally, review and restrict the permissions granted to the DuckDB user account to limit the potential damage from a successful SQL injection attack. After upgrading, confirm the fix by attempting to inject a simple SQL statement and verifying that it is properly sanitized.