it seems patched on 18362.295, however on 18362.239 I could not write to /windows/Temp as a lowpriv fellow. This restriction can be obviously bypassed by creating a c:\temp folder and edit line 424 to: set r2 5c504d45545c3a63https://twitter.com/taviso/status/1161277080723529728 …
-
-
Replying to @matteomalvica
Hmm interesting, I probably should have been more thorough finding somewhere. It worked on a few test machines, but I guess it's not as universal as I assumed!
2 replies 0 retweets 1 like -
Replying to @taviso
Anyhow, I am wondering how the patch from today has been implemented, do you have any insights?
1 reply 0 retweets 0 likes
Replying to @matteomalvica
My understanding is they now verify matching session on connect and fixed the memory corruption bugs - I don't think this is a complete fix (and there for sure will be more memory corruption), but will need some time to analyze it.
2:06 PM - 13 Aug 2019
0 replies
0 retweets
2 likes
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.
research today, a major design flaw in Windows that's existed for almost *two decades*. I wrote a blog post on the story of the discovery all the way through to exploitation.