I would like to thank @msftsecresponse for the bounty. Just days before Ramadan. https://twitter.com/waleedassar/status/1377606227249729537 …pic.twitter.com/GJ6ZgrKepJ
-
I see, still doesn't explain them paying for it. Traditionally they'd mark that as a reliability issue, not even security. But hey, get them to pay while before they change their mind. Hopefully it won't end up like the great symlink bounty scandal
I spiced it a bit up with a POC with .url file where the icon points at the path. I made it for the volume corruption bug, but also gave bleeping computer a POC that just BSOD - the rest is history. But yarh, now they gotta pay up for this kinda BSOD.
-
-
if they fix .url I have others.... its just a sympton, not the root cause
-
Well it doesn't require much imagination to work out that you can abuse .url or .lnk files and similar if you have a bug where just poking a file path causes a crash. Sadly, the one thing I can say with certainty is MS lacks such basic skills :-)
End of conversation
New conversation -
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.