Security fix: open redirect vulnerability in case of 'unknown client_id' #64
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
…oes not set the error_url to prevent open redirect attacks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As outlined in IdentityPython/SATOSA#498 , SATOSA returns a redirect to an unvalidated redirect_uri if the client is unknown, which is an "open redirect" vulnerability. The root cause is obviously in pyop, because it raises an InvalidAuthenticationRequest with a non-empty error_url if the client is unknown.
I have added a specific exception UnknownClientId which returns no error_url, just as the InvalidRedirectURI exception does.