We have confirmed this POC to work and in fact provide read access to a chosen file that the initiating user didn't have read access to. https://twitter.com/Evil_Polar_Bear/status/1075605011105767424 …
-
This Tweet is unavailable.
-
Replying to @0patch
I haven't seen anything other than a pegged CPU. The VM in question has 4 cores. ¯\_(ツ)_/¯pic.twitter.com/HHMFcJQDLd
1 reply 0 retweets 1 like -
Replying to @wdormann
It is a race condition issue, and your race was lost :) Did you also try the desktop.ini from another user?
2 replies 0 retweets 1 like -
Replying to @0patch
I didn't, as I can seem to do that without any trickery.pic.twitter.com/GP81bGkAU3
1 reply 0 retweets 0 likes -
Replying to @wdormann
That shouldn't be possible. Are you running the POC as admin?
1 reply 0 retweets 0 likes
Yeah, I'm failing to understand why it was possible. Perhaps something went wonky in my failed attempt? In that same VM, my "test_user" home directory gives full permissions to the newly-created "limited" account for some reason. Reverting and trying again shows the PoC workingpic.twitter.com/qJCeZyBFKy
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.