CRE-2025-0163: Supabase Self-Hosted Critical Failures - Comprehensive Detection #154
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
piyzard
changed the title
tonymeehan
reviewed
Sep 3, 2025
| - "https://supabase.com/docs/guides/self-hosting/docker#troubleshooting" | ||
| - "https://github.com/supabase/supabase/discussions" | ||
| - "https://supabase.com/docs/guides/platform/performance" | ||
| scores: |
There was a problem hiding this comment.
@tonymeehan troubleshooting docs for reference,
should i change it ?
There was a problem hiding this comment.
hi piyush, tony was referring to the fields scores, cvss, cvss_security,cwe. the are not supported in the CRE definition. please remove them
|
Hi @piyzard thanks for submitting the CRE! please take a look at the merge conflicts (due to same CRE ID) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CRE-2025-0163: Supabase Self-Hosted Critical Failures - Comprehensive Detection
closes #131
/claim #131
🎯 Overview
This PR introduces a comprehensive detection rule for Supabase self-hosted deployment failures - addressing critical infrastructure, configuration, and application-level issues that completely break Supabase deployments. The rule identifies 40+ distinct failure patterns across PostgreSQL, Auth, Storage, Realtime, and API Gateway components, enabling rapid incident response for complete service outages.
CRE Playground Links
CRE-2025-0163 Playground: Test Rule
📊 Supabase Failure Modes Covered
🔴 Infrastructure Failures (Critical)
Error: listen EADDRINUSE :5432bind: address already in use :9999No space left on deviceSSL certificate expiredTLS handshake failed🔐 Authentication & Security Failures
JWT_SECRET not setinvalid jwt secretJWT secret too shortcertificate verify failed🗄️ Database Connection Failures
connection timeoutcould not connect databasetimeout expiredtoo many connections📦 Storage Service Failures (S3)
S3 AccessDeniedInvalidAccessKeyIdNoSuchBucketPermission denied🔄 Realtime & WebSocket Failures
Realtime failed to startwebsocket connection refusedsubscription failed🚨 Migration & Schema Failures
ERROR syntax error at or nearmigration failed invalid SQLrelation does not existschema version conflict⚡ API Gateway & Rate Limiting
429 Too Many RequestsRate limit exceeded504 Gateway Timeout🧪 Testing & Validation
cat rules/cre-2025-0163/test.log | preq -r rules/cre-2025-0163/supabase-comprehensive-failures.yaml -d🎬 Demo Environment
Screencast.from.2025-09-01.14-57-08.mp4
Demo Repository: https://github.com/piyzard/cre-2025-0163-supabase-failures
📚 References