Skip to content

feat: Add SQL parsing validation to RLS clauses to prevent SQL injection - #8

Open
sha174n wants to merge 2 commits into
masterfrom
rls-clause-validation-4104895394640590304
Open

sha174n wants to merge 2 commits into
masterfrom
rls-clause-validation-4104895394640590304

Conversation

@sha174n

@sha174n sha174n commented Feb 23, 2026

Copy link
Copy Markdown
Owner

This PR adds a validation layer to Row Level Security (RLS) clauses to prevent SQL injection attacks, specifically targeting boolean-based blind SQL injection via subqueries.

Changes:

  • Added superset.utils.rls.validate_rls_clause function.
  • This function uses sqlglot to parse the RLS clause and ensures it does not contain:
    • Multiple statements (stacked queries).
    • Forbidden node types: Subquery, Select, Values, Union, CTE, DDL, Command, Delete, Insert, Update, and Mutation.
  • Integrated validation into CreateRLSRuleCommand and UpdateRLSRuleCommand in superset/commands/security.
  • Raises marshmallow.ValidationError if the clause is invalid, which is handled by the API to return a 422 error.

Tests:

  • Verified with isolated unit tests covering valid clauses, invalid subqueries, unions, and DDL attempts.
  • Verified command integration with mocked tests.

PR created automatically by Jules for task 4104895394640590304 started by @sha174n

Introduces strict validation for Row Level Security (RLS) clauses to prevent SQL injection.
- Adds `validate_rls_clause` utility using `sqlglot` to parse and check for forbidden SQL constructs (subqueries, CTEs, mutations, etc.).
- Updates `CreateRLSRuleCommand` and `UpdateRLSRuleCommand` to enforce this validation.
- Addresses a potential boolean-based blind SQL injection vulnerability where subqueries could be used to exfiltrate data.

Co-authored-by: sha174n <105581038+sha174n@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

- Fix MyPy error by annotating `forbidden_types` tuple with `type[exp.Expression]`.
- Fix MyPy error in `CreateRLSRuleCommand` by ensuring `validate_rls_clause` receives a `str`.
- Fix Unsorted imports in `superset/utils/rls.py`, `superset/commands/security/create.py`, and `superset/commands/security/update.py` to satisfy Ruff.
- Remove unused `ValidationError` imports in commands.
- Ensure RLS clause validation handles `exp.Delete`, `exp.Insert`, `exp.Update` which are not subclasses of `exp.Command` in sqlglot v29.

Co-authored-by: sha174n <105581038+sha174n@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant