-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positive Enforcement #130
Comments
Interesting point, Ill make some research and see what is the ideal solution, will keep you posted, thanks for reporting this |
authorization/authorization.py allowed_status_codes = ["200", "302", "301", "303", "307", "308"] What about adding this logic? (other status codes do not seem to need to be checked) |
But if the new status code is still 302, it will return True and will be marked as enforced, im not sure how it helps |
Here's what I think: |
There is a specific case of false positive in the check_bypass function.
I encountered a web application which returns a 302 and redirect to
/
but also returns the privileged data in the body. So it's categorized as "Enforced" but actual sensitive data is still returned.I understand that it's there so that it works out of the box without having to define enforcement filters, but it would be great to have an option to just bypass this check and only use enforcement filters.
The text was updated successfully, but these errors were encountered: