Repository navigation
fix(database): restrict workspace service RPCs - #64
Conversation
Co-Authored-By: Claude Code <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe migration restricts workspace thread-generation functions to ChangesWorkspace ACL Hardening
Estimated code review effort: 2 (Simple) | ~10 minutes Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Production follow-through verified:
No Edge Functions changed in this follow-up, so none were redeployed. |
Summary
anonandauthenticatedexecution from the two server-owned workspace generation RPCsProduction finding
Post-merge catalog verification found that Supabase default privileges left
authenticatedable to executestart_workspace_thread_generationandcomplete_workspace_thread_generation. Both accept server-supplied user IDs and are intended forservice_roleonly.Verification
ROLLBACKsupabase db push --dry-runlists only20260922233256_harden_workspace_function_acl.sql🤖 Generated with Claude Code
Summary by CodeRabbit
Security
Tests