Vulnerable/Wildcard CORS Policy - #2041
Conversation
|
@ArshVermaGit is attempting to deploy a commit to the ritesh Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
More reviews will be available in 17 minutes and 10 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ArshVermaGit
left a comment
There was a problem hiding this comment.
Hi @ritesh-1918 ! The issue has been resolved. Please review the PR and merge it under GSSoC. Thanks!
|
Hi @ArshVermaGit! Thanks for the contribution. I have triaged your PR and set it to merge into the
Welcome to the HELPDESK.AI developer family! 🚀💻 |
1a0f672
into
riteshbonthalakoti:gssoc
Changes Made:
backend/main.pyCORS middleware.allow_methods=["*"]with an explicit list:["GET", "POST", "PATCH", "OPTIONS"].allow_headers=["*"]with an explicit list:["Content-Type", "Authorization", "Accept"].By explicitly declaring only the capabilities actually utilized by our frontend client, we massively reduce the API attack surface area. This ensures that even if an attacker manages to hijack an approved origin, their ability to execute destructive, unverified HTTP behaviors or inject malicious headers is structurally blocked by the browser.
Resolved Issue
Resolves #2040