Comment Re: Not 0day (Score 1) 44
I was curious to about the 90 day requirement so read the GitHub. Windows switches to "enforcement mode" when parsing log files after 90 days. Since windows parses log files in kernel mode, its a big target in the past. If you create a log file container and in the same user process, then trigger the antimalware, it will elevate the user process. It looks like somone forgot to put the right restrictions on creating the files log containers use? I still cannot figure how can a user process be upgraded silently in all these windows exploits. It feels like Microsoft hates switching between user/kernel mode and relies on security permissions to much. I checked the code
Its 5am so I might of missed something. The report SHOULD read "90 days after you have updated to Windows 26H2, you may be vulnerable"