I can confirm that these actions do appear to prevent the Windows Task Scheduler LPE exploit code from working. However, it's not clear at this point what sort of collateral damage one might experience by making these changes...https://twitter.com/karsten_nilsen/status/1034406706879578112 …
-
-
Yah, I’m just saying in an Enterprise I wouldn’t recommend it - it will break stuff.
-
I don't dispute that *something* would break. I'm just curious as to *what* might break. Given that limited users can still schedule their own tasks after setting the ACLs, there may not be too much collateral damage. I'd like to know a specific example of something that breaks
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.