Optimize SchieldBreak to work in windows 10 - #4
Conversation
Hi, @MSNightmare Windows 10 not supported but yeah, we improved the exoloit for windows 10 too do'nt worry, means will work in all windows versions
That’s a nice change; I suggest testing it on Mars before bringing it back to Earth for pull. |
|
I'm catching a space shuttle to Mars next week, if this works there I'll push it. |
|
Just my 2 cent, guys I think for this PR it's best to use the Moon as a QA env, then test on Mars for production use case. |
| #define ROWS 5 | ||
| #define COLS 5 | ||
|
|
||
| int main() { |
|
@MSNightmare can you stop dropping exploits, please, can you apoligze to microsoft or report them to a coordinator for coordinate with them for the next zero days |
|
@MSNightmare many exploits are heavily exploited by threat actors, like SchieldBreak there was no patch at all, you putting users at risk can you apoligze to microsoft, if you report further findings to a coordinator and then the coordinator will coordinate with microsoft patch |
|
@HackingRepo Why won't Microsoft just patch those exploits if they are exploited by threat actors ? Are they just stupid ? |
No they do patch them but because you deploy your exploits right after a Patch Tuesday you maximize the time of the Vulnerability being Non-Terminated and that time is abused by threat actors |
|
Gotta love people defending Microsoft, but if this is critical they should deal with it, threat actors don't wait for Patch Tuesday to start using 0 days. @MSNightmare at least shows everyone that Microsoft Windows 11 is insecure and publishes the proof for everyone to see and test. EDRs/SIEM agents could probably attempt detection and block this behavior. (I doubt however that EDRs can run along Defender but I've seen it happen already due to probable some misconfiguration or bug). Blue team could run this in a controlled lab to check for specific detection logs/forensic clues. Finally, what if this 0 day was already in the hands of private threat actors and @MSNightmare found it by himself through pure technical skill and just burned it for free by publishing it, no matter how I look at this, this repository improves security awareness. I do get that a coordinated report is better but Microsoft has been treating previous work of @MSNightmare pretty poorly until they deleted his account for vulnerability report. I dont think he should bother with MSRP again. Given what happened. That Microsoft isn't patching this until the next Patch Tuesday => shows Microsoft doesn't have the means or will to patch it with a hotpatch, shows how much they care about their customer security. |
|
@AkechiShiro
Correct no one is denying his skills he is good but that doesn't mean that he should publish it and let threat actors use it just because of a Personal Feud if you see that he has the right to do that then you are Delusional that shit is personal and because you nuked the factory i am working in you did cut my way of making money the same way it translates here Third
Hot patching is a Terrible idea now Engineers do make mistakes like how they didn't patch RoguePlanet correctly When Dave Cutler did work on the NT Kernel and was released later so instead of saying when you attempt to criticize you'd attempt to criticize in a valid way And not This way
PLUS your bio |
|
I stand by my point, I understand your argument, but listen, we wouldn't have been arguing had MSRP done its job properly. Cultural change is needed, if that causes damage for customers, that's customers issues, they should raise their concern to Microsoft's way of treating 0 days researchers. No one should be in support of a company actively closing cybersecurity researcher accounts when they report 0 days just to avoid paying them for their work, we can probably agree that's unfair. If they keep doing it, you'll see more @MSNightmare than you ever want to, and arguing here isn't gonna change anything. So keep working on your patch to fix ShieldBreak and apply for Microsoft Security Team, that way you can fix @MSNightmare 0 days as fast as he publishes them someday for sure. |
i agree with some of your points but not all Yes no one should be supporting a company that treats 0 day researchers badly i fully stand by that point Arguing wont do any effect. You are Wrong if you don't care about these then you'd never succeed so what is your excuse next time ? |
|
If a corporation is doing something bad, staying silent is not good IMO. Finally, your main point stands, and I understand that researcher shouldn't do this AFAIK under optimal condition (where responsible disclosure works pretty well), but when responsible disclosure is not working for said researcher multiples times, he's not going to bother doing it more and more with a corporate company that deleted his own account for the responsible disclosure, that's all there is to it, you can open issues, argue with the researcher he's probably not gonna change his mind ever, that's what I meant when I said arguing is pointless here. You don't need to argue here because you're not going to change @MSNightmare's mind or stance on this matter. Only thing that could help is MSRP/MS adressing this publicly or privately by reaching out to @MSNightmare and discussing how they could rebuild the bridge of trust that was burned by their own hands. |
if he never stops i would never stop until i am dead or he is dead Your Opinion would never stand because they never stayed silent anyway defender already does detect the signature of it anyway second he'd never change his mind Build Trust ? the only problem of what he is doing is just and I Am not saying that Microsoft was never wrong so whatever what you say next is not going to change anything anyway i am Ending it Here say whatever what you want to say I am waiting to see what is next MSN... |
|
I known, but can you use a coordinator, instead of MSRC for future reports, and will be patched safely, that way is bad, attackers are weaponizing those exploits, that what i'm worry, do'nt use MSRC @MSNightmare use a coordinator, and then will coordinate with microsoft to patch the exploits |
Hi, @MSNightmare
Windows 10 not supported but yeah, we improved the exoloit for windows 10 too do'nt worry, means will work in all windows versions