Add flask-cors-misconfiguration rule #3506
Merged
Conversation
This file contains 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
0xDC0DE
reviewed
Nov 12, 2024
|
Hi! @lfama Thanks for your contribution, this rule looks good! I've made a suggestion to improve your rule slightly. If you address this and the CI checks pass, we can merge this. 🥇 |
0xDC0DE
approved these changes
Nov 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi!
I've created a simple rule that matches flask_cors misconfiguration.
Basically when setting
origin="*"andsupport_credentials=Trueflask_cors dinamically reflects the Origin of each request in theAccess-Control-Allow-Originheader which together withAccess-Control-Allow-Credentialset to true can be dangerous.