Hi! I'm the person in charge of managing the bug bounty program, and I'd like to shed light on what happened from our end. I already apologized and explained this to @0xcrypto internally, but I believe that I should say something here to clarify what happened. The truth here is that we were never able to fully reproduce the issue from the beginning, but struggled to close it because of the fear of missing something.…
Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
91–100 of 114 posts
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#92How can I solve this problem cheaply? Here are a few thoughts: - Generate an encrypted token based on the redirect state value. - Store the mapping of tenant_id and unique state. - wait Microsoft support wildcard redirects.
First, just don't enable implicit grant. That makes it a lot harder to screw up. State is for preventing CSRF, not transferring data. Don't abuse state, it's wrong. Use your own authorize url, add an encrypted cookie and redirect to the real one. Even if the cookie is encrypted, only put some kind of session/cache key in it, don't actually send "info". Read cookie in callback then delete it.
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#93Hi! I'm the person in charge of managing the bug bounty program, and I'd like to shed light on what happened from our end. I already apologized and explained this to @0xcrypto internally, but I believe that I should say something here to clarify what happened. The truth here is that we were never able to fully reproduce the issue from the beginning, but struggled to close it because of the fear of missing something.…
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#94Earlier quoted context omitted.
It's kinda normal that you'd want to let a user log in and return them to the page they were at. For example, if you're making a shopping website and a user asks to put something in their basket and you send them to log in, you'd want to return them to the item they were about to buy, not dump them back at the homepage. What's the proper way of doing this, without "abusing state" ?
Store the basket in a temporary cookie, not the oauth state parameter.
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#95Hi! I'm the person in charge of managing the bug bounty program, and I'd like to shed light on what happened from our end. I already apologized and explained this to @0xcrypto internally, but I believe that I should say something here to clarify what happened. The truth here is that we were never able to fully reproduce the issue from the beginning, but struggled to close it because of the fear of missing something.…
Also, it is still unclear how you wanna continue with the report since it is no longer reproducible. I would have discussed it further on Hackerone but apparently I have been ghosted again after the apologize message.
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#96Hi! I'm the person in charge of managing the bug bounty program, and I'd like to shed light on what happened from our end. I already apologized and explained this to @0xcrypto internally, but I believe that I should say something here to clarify what happened. The truth here is that we were never able to fully reproduce the issue from the beginning, but struggled to close it because of the fear of missing something.…
Well mistakes happen. One thing that is still not explained is that I contacted Hackerone many times in the timespan of 3 years but they couldn't get in contact with you either. Also, it is still unclear how you wanna continue with the report since it is no longer reproducible. I would have discussed it further on Hackerone but apparently I have been ghosted again after the apologize message.
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#97Earlier quoted context omitted.
He manages the big bounty program. Why would you think he would be interested in your personal UX issues with the app?
I think you have a wrong impression of the size of the company. According to their website they have 26 engineers in total. And I would doubt that those are my "personal" UX issues.
Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#98Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#99Re: Stealing OAuth tokens of Microsoft accounts via open redirect in Harvest App
#100Earlier quoted context omitted.
Microsoft checks the return URL to see if it is one of the whitelisted URLs specified by Harvest. Harvest added their own redirection mechanism on top of this, presumably to support multiple instances of their software, which did not do a good job of sanitizing input values for their redirect. So no, this is not an implicit issue with oauth, just a shoddy implementation.
Ok, I think I understand but correct me if I'm wrong. Normally that return URL would be hidden from view, as it would live in configuration detail found inside of the Microsoft system, attached to the client_id. However, Harvest weakened this security by adding in the additional (and unsafe) return_to parameter to manage their return URL.