supabase-postgrest-rls-v2
5 rules · Keryn Software Licence · rules 0.8.0 · all packs
How to read a rule
- Severity
- How bad the finding is if it is real:
errorfails a default gate,warningandinfodo not. - Confidence
- P0 exploitable as written; P1 dangerous in context; P2 a heuristic or a posture check: confirm by reading the code.
- False-positive risk
- low: an exact API or flag, so hits are almost always real; medium: the pattern is legitimate in many programs, so check each hit; high: it finds a lead to confirm, so expect benign hits.
- Edge
- The relationship the finding sits on. reaches: content or traffic gets to a thing; calls: one thing invokes another; reads: one thing reads from another; writes: one thing writes to another; sends: data leaves for another party; grants: authority is given or left unchecked; depends_on: something relies on a component it does not verify; trusts: one party believes another without evidence. The boundary it crosses, when there is one: user->prompt (untrusted input reaching a prompt); model->code (model output reaching code, a shell, a query or a page); secret->outside (a secret leaving the trusted side); supply-chain (code, models or prompts pulled in from outside).
- Taxonomy chips
- References for readers who work in OWASP LLM 2025, OWASP Agentic, CWE or NIST AI RMF. They say where a rule belongs, not that a framework is satisfied.
seceng.supabase.postgrest-public-table-ai-data
Section titled “seceng.supabase.postgrest-public-table-ai-data”warning typescript, javascript supabase, postgres
Supabase/PostgREST configuration appears to expose AI data tables through public schema or anon role.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: grants authority is given or left unchecked.
CWE-732 CWE-200 LLM02 LLM08 ASI06 ASI03
seceng.supabase.rls-not-enabled-for-ai-table
Section titled “seceng.supabase.rls-not-enabled-for-ai-table”warning generic supabase, postgres
AI data table is created without a nearby ALTER TABLE ENABLE ROW LEVEL SECURITY statement.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: grants authority is given or left unchecked.
seceng.supabase.rls-policy-without-auth-uid
Section titled “seceng.supabase.rls-policy-without-auth-uid”warning generic supabase, postgres
RLS policy for AI data table does not visibly reference auth.uid() or tenant membership logic.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: grants authority is given or left unchecked.
seceng.supabase.postgrest-openapi-exposes-ai-tables
Section titled “seceng.supabase.postgrest-openapi-exposes-ai-tables”info generic supabase, postgres
PostgREST/OpenAPI configuration appears to expose AI tables or functions that may contain prompt, memory, embedding, or transcript data.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: reaches content or traffic gets to a thing; it crosses the user->prompt boundary (untrusted input reaching a prompt).
CWE-200 LLM02 LLM07 LLM08 ASI06
seceng.supabase.sql-security-definer-ai-function
Section titled “seceng.supabase.sql-security-definer-ai-function”warning generic supabase, postgres
SECURITY DEFINER function touching AI/RAG tables can bypass caller RLS. Verify strict ownership and search_path controls.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: calls one thing invokes another; it crosses the model->code boundary (model output reaching code, a shell, a query or a page).