SQLi in llmware collection-database backends causes cross-document disclosure

Key Vulnerability Information Summary Vulnerability Overview Title: SQL Injection: Unescaped metadata/filter values in the collection-database layer leading to cross-document disclosure Issue Number: #1304 Status: Open Type: SQL Injection (SQLi) Impact: An attacker can craft malicious filter values so that a benign filter condition, which should return 0 rows, instead returns 1 row, thereby disclosing other documents (cross-document/cross-collection disclosure). Scope of Impact Affected Components: 's SQLite and PostgreSQL collection-database backends Vulnerability Locations: - in (around line 2329): filter values are directly concatenated into the SQL string without parameterization or escaping. - The PostgreSQL backend exhibits the same pattern ( around lines 1200, 1239), with constraints that do not restrict case sensitivity or UNION keywords. - Value Sources: Public API , ( around line 1205), and / within ( around lines 532, 540). - In RAG or multi-tenant deployments, these values originate from end-user input or document metadata fields. Remediation Plan Change filter values to be bound using SQL parameters ( placeholders) instead of string concatenation. The page footer displays the remediation progress: - submitted a commit referencing this issue ( , commit ). - Related Pull Request: #1310 ( ), intended to close this issue. POC / Exploitation Code No standalone POC code block is provided on the page, but code snippets showing the vulnerability trigger points are displayed (the concatenation logic of in ): This snippet illustrates the injection point where is directly concatenated into the SQL string.

Goal Reached Thanks to every supporter — we hit 100%!

SQLi in llmware collection-database backends causes cross-document disclosure

More from this source