Open redirect in rfc6749 aka 'The OAuth 2.0 Authorization Framework'
an attacker:
Then the attacker can craft a special URI of the form http://victim.com/authorize?response_type=code&client_id=bc88FitX1298KPj2WS259BBMa9_KCfL3&scope=WRONG_SCOPE&redirect_uri=http://attacker.com
according to Section 4.1.2.1 this should redirect back to attacker.com (without any user interaction, ever...)!!! Here we use the a wrong scope parameter but any reasons other than a missing or invalid redirection URI would had make the trick....
<aside> 💡 Sometimes in order to accomplish some sort of attack you need to have an open redirect. This is only one small part of the chain but an essential one.
</aside>
How Microsoft is giving your data to Facebook... and everyone else
try to modify “redirect_uri” parameter you’ll notice that token is issued to any URL within facebook.com domain
So to leak the OAuth token to a malicious third-party an Open Redirect in facebook.com domain would be required.
Url Decoded ⇒