3
Allow Access-Control-Allow-Origin (CORS) policy to be set via dashboard
Source: supabase/supabase#36693 · opened by @cmcnicholas
We have recently had our product pen-tested externally and a key point was about limiting access to authentication API's as the current CORS policy allows all Access-Control-Allow-Origin: * > Cross-origin Resource Sharing (CORS) Misconfiguration Cross-origin Resource Sharing (CORS) is a security feature implemented in web browsers to prevent unauthorised access to resources from different domains. However, if not properly configured, it can be exploited to allow arbitrary origins, leading to potential data leakage or unauthorised actions. In this case, our system has been found to trust arbitrary origins, which means it's currently possible for external websites to access our resources without proper authorisation. This misconfiguration could allow sensitive data to be exposed or malicious actions to be performed, posing a significant risk to our organisation's security and privacy It would be beneficial to be able to set this explicitly in the dashboard, this …
No pledges yet. Be the first to back this.
Comments
Similar requests
CORS settings for Storage S3
6 votes · 0 comments
Login Issue: CORS Policy & Preflight Redirect Error on auth.supabase.io
2 votes · 0 comments
Make it possible to view raw RLS policy SQL in the Supabase Dashboard
18 votes · 0 comments
[splinter] Proposal: two INFO lints for grant/policy mismatch (privilege_without_policy, policy_without_privilege)
1 vote · 0 comments
Move RLS verification into the policy editor, not beside it
1 vote · 0 comments
No comments yet.