You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
That is the only case where I can see an not content controllable file creation vulnerability being usefull. Remember, a file creation vuln is also a directory creation vuln. Just append ::$INDEX_ALLOCATION
I Just got an idea.... You can create an alternative data stream on the primary hard drive root C:\:stream:$data - then afterwards you can open the file with FILE_APPEND_DATA because of FILE_APPEND_DATA S-1-5-11 (NT AUTHORITY\Authenticated Users)
Since the file is empty you now control 100% the content of a file that have a location that is likely to be unexspected. Create an symbolic link in NT Object Namespace with .exe targetting it to execute the file. That is a persistence technique thats easy to miss :)
Dir /R executed in C:\ will not even show the file
That would certainly work assuming it's not setting some super restrictive ACL explictly though. Of course you'd still need to find something useful to do with that primitive :-(
Making \??\UNC\;CSC\.\.::1\C$:$data:$data:$data:$data a valid file is usefull to me :)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
