3 ms·
I am not sure if this is still the best approach. They did not even try to submit based on expected "low" ranking when comparing to existing XSS submission. The
by nicce 4mo ago
I am not sure if this is still the best approach. They did not even try to submit based on expected "low" ranking when comparing to existing XSS submission. They should at least try or let them know many days before disclosing. You never know.
- jeremyjh 4mo agoIts not just one issue they mishandled. It is a pattern. I think this makes sense if you believe long-term security requires leadership change at MSRC. https://doublepulsar.com/microsofts-stance-on-zero-day-exploits-is-a-dumpster-fire-of-their-own-making-0946117940a4 https://doublepulsar.com/microsofts-stance-on-zero-day-explo...
- ammar2 4mo agoIt's not just based on that, if you read the linked report from 2023 (https://blog.ammaraskar.com/vscode-rce/ https://blog.ammaraskar.com/vscode-rce/), I had a bug with the exact same impact of token exfiltration (It did need one additional click on the VSCode interface). They marked it as low severity, fixed it silently, didn't acknowledge that it had security impact and did not provide me any credit much less a bounty.
- nicce 4mo agoI thought that the general issue was that they ignore the submissions and do not fix them - but the actual problem is that they give different severity and may not give fame or money? I think disclosure for those reasons is highly in gray area from ethical perspective. Regardless if it was clearly in the scope of the bug bounty program or not. That is distinct problem and does not justify public disclosure without warning with enough time.