Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

supabase-community/database-build
main @ de2c18d
5
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Auth Bypass: 3 prior fixes. Scrutinize any change in this area.
apps/browser-proxy/src/index.ts: most-fixed (3 issues). Treat as high-risk during review.
2 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: The WebSocket proxy interface previously allowed unauthenticated connections to bypass live-sharing restrictions. Validating the Supabase user token via supabase.auth.getUser is mandatory for all connection upgrades.
Auth Bypass: The AI chat interface and CSV file ingestion handlers lacked user identity verification, allowing anonymous users to invoke costly AI workflows. Gating these actions behind GitHub OAuth is necessary to protect downstream resources.
Denial of Service: Unbounded socket lifetimes and idle connections in the browser-proxy were capable of exhausting available system file descriptors, requiring explicit connection limits.