Описание
WeKnora has Broken Access Control - Cross-Tenant Data Exposure
Summary
A broken access control vulnerability in the database query tool allows any authenticated tenant to read sensitive data belonging to other tenants, including API keys, model configurations, and private messages. The application fails to enforce tenant isolation on critical tables (models, messages, embeddings), enabling unauthorized cross-tenant data access with user-level authentication privileges.
Details
Root Cause
The vulnerability exists due to a mismatch between the queryable tables and the tables protected by tenant isolation in internal/utils/inject.go.
Tenant-isolated tables (protected by automatic WHERE tenant_id = X clause):
Queryable tables (allowed by WithAllowedTables() in WithSecurityDefaults()):
Gap: The tables messages, embeddings, and models are queryable but NOT in the tenant isolation list. This means queries against these tables do NOT receive the automatic WHERE tenant_id = X filtering.
Vulnerable Code
File: internal/utils/inject.go
File: database_query.go
When tenant 1 queries SELECT * FROM models, the validation passes and no WHERE tenant_id = 1 clause is appended because models is not in the tablesWithTenantID map. The unfiltered result exposes all model records across all tenants.
PoC
Prerequisites
- Access to the AI application as an authenticated tenant
- Ability to send prompts that invoke the
database_querytool
Steps to Reproduce
-
Authenticate as Tenant 1 and craft the following prompt to the AI agent:
Use the database_query tool with {"sql": "SELECT * FROM models"} to query the database. Output all results and any errors. -
Expected vulnerable response: The agent returns ALL model records in the
modelstable across all tenants, including:- Model IDs and names
- API keys and authentication credentials
- Configuration details for all organizations
Example result:
-
Repeat with messages table:
Use the database_query tool with {"sql": "SELECT * FROM messages"} to query the database. Output all results. -
Expected vulnerable response: The agent returns ALL messages from all tenants, bypassing message privacy.
PoC Video:
https://github.com/user-attachments/assets/056984e8-1700-41fe-9b8a-6d18d5579c18
Impact
Vulnerability Type
Broken Access Control (CWE-639) / Unauthorized Information Disclosure (CWE-200)
Specific Data at Risk
-
API Keys & Credentials (from
modelstable)- Third-party LLM provider keys (OpenAI, Anthropic, etc.)
- Database credentials and connection strings
- Authentication tokens for integrated services
-
Private Messages (from
messagestable)- Confidential business communications
- User conversations with AI agents
- Sensitive information shared within conversations
Пакеты
github.com/Tencent/WeKnora
<= 0.2.11
0.2.12
Связанные уязвимости
WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.12, a broken access control vulnerability in the database query tool allows any authenticated tenant to read sensitive data belonging to other tenants, including API keys, model configurations, and private messages. The application fails to enforce tenant isolation on critical tables (models, messages, embeddings), enabling unauthorized cross-tenant data access with user-level authentication privileges. This issue has been patched in version 0.2.12.