Any additional info from @msftsecresponse on the "potential impact of this method" after their review? 
-
This Tweet is unavailable.
-
-
Replying to @GaborSeljan @the_secret_club and
they just agree that it is not a vulnerability, and they ask me to keep information about the arbetary file delete vulnerability in storage service confidential untill they patch it.I submitted the vulnerability together with with method from article. They say it is is not bounty
1 reply 0 retweets 2 likes -
Replying to @jonasLyk @GaborSeljan and
eligable because either it is for a product not in bounty scope, it have been submitted previously or its impact is not rated serious enough.
1 reply 0 retweets 0 likes -
Replying to @jonasLyk @GaborSeljan and
Probably you were not the first to submit the bug. But if you ask for more detailed info they usually will answer you telling you the exact reason.
1 reply 0 retweets 0 likes -
Replying to @decoder_it @GaborSeljan and
no, they just lie and make something up- when confronted they ignore you.
2 replies 0 retweets 0 likes -
Replying to @jonasLyk @decoder_it and
last time they ignore me for two months, then they claim dupe. But I talked with other person acknowledged for the bug, and he had not submitted it. Mine was rated EOP, POC was provided, should have given decent bounty. He had 0 EOP in that service- how the hell can it be a dupe?
1 reply 0 retweets 0 likes
And mine was triaged, i use one information disclosure bug to trigger the eop. MS somehow judge that both my submissions was dupe of other submission. But in reality they just waited for someone to submit something in the same service so they could scam me- and only pay him 1000$
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.