this post was submitted on 11 Jun 2026
181 points (100.0% liked)
PC Master Race
21357 readers
575 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: especially when new beginners have questions.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is not surprising.
The industry knowledge had by the thousands of engineers laid off has to go somewhere.
Well when you report a bug to ms and they respond with disabing your account and you then release the 0day the ms responds with a public blog post saying people who release 0 days are breaking the law and liable for legal action of cause you then drop a second 0day and ms responds by retracing the legal threat so you you now drop a third one while your account to report these bugs is still disabled. What else would you do?
lol is this cheaper than just paying the fucking bounty? I'm beginning to wonder.
How could it be? Any news is good news.
Companies who use Microsoft don't care about security
Drop a 4th one?
They did this is the 7th with more to come.
2nd bitlocker backdoor
I look forward to it.
This is not about that. This is about a security researcher that wasn't paid by Microsoft's bug bounty program when they found a security bug.
Bug bounty programs exist to prevent this exact scenario. To give people a reward for privately disclosing the vulnerability with the devs instead of publicly/to a bad actor.
AMD fucked up recently about that as well. It seems big tech is getting so arrogant and so far up its own ass that they can't even admit to bugs anymore, which is problematic considering their sloppy AI slop never had so many bugs as it does now.
Honestly, it's the opposite: AI is exposing so many bad security bugs that they are having a hard time keeping up.
That's overblown. Yes, people are finding security bugs with AI, you will always get that when adding new tests with a different perspective. But the "having a hard time keeping up" come from the AI constantly spamming devs with duplicate issues.
NIST has already updated their CVE policies because of "record CVE growth".
Hmmmm, I wonder wtf happened during those years?