HexBrain

X / xAI · Report #166942

leaking Digits OAuth authorization to third party websites

Validstatus
13upvotes
24 Jan 2017disclosed

Summary

A better attack vector was also identified by chaining OAuth callbacks Example

https://www.digits.com/login?consumer_key=F1vVaDqvmTQbtoxYhzR6baV55&host=http%3A%2F%2Fwww.digits.com&callback_url=https%3A%2F%2Fwww.digits.com%2Flogin%3Fconsumer_key%3DmQQYhgvULqx2UPW8Za8iESZOy%26host%3Dhttps%3A%2F%2Fwesecureapp.com%2F%26callback_url%3Dhttps%3A%2F%2Fwesecureapp.com%2F

Upon navigating to the above URL, you will be presented with digits App, once you click Authorize you're redirected to attackers application and if you authorize that application too you will be redirected to attackers website with digits token as a referrer.

How it was found

Hi,

While authenticating digits to my Fabric account i have noticed that the callback_url is not solid i.e. any sub domain or any path is accepted as callback_url with host as fabric.io. This issue can be exploited by leaking the authorization token to third party websites (websites mentioned on kit's page)

Steps to reproduce:

This issue can also be exploited on our organization member by actually leaking the consumer secret to our domain.

Steps to reproduce

Regards, Akhil

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original