4 ms·
Not sure why you're getting downvoted, but debugging a "crack me" app while running as root is probably a bad idea. Even if this is inside a VM, it might give
by scott_karana 12y ago
Not sure why you're getting downvoted, but debugging a "crack me" app while running as root is probably a bad idea.
Even if this is inside a VM, it might give the wrong message to someone wanting to try this for themselves.
- ryan-c 12y agoI've played in many CTFs and written challenges for a few. Unpleasant surprises in the binaries, especially when run as root aren't uncommon.
- eyeareque 12y agoYou could also attack the VM: http://www.cvedetails.com/vulnerability-list/vendor_id-93/product_id-20406/Oracle-Vm-Virtualbox.html http://www.cvedetails.com/vulnerability-list/vendor_id-93/pr...
- doreo 12y agoChrist I had no idea Virtualbox was that riddled with holes. I wonder how many of those have been fixed.
- jfoster 12y agoGiven this, what is the best first step? Best we can tell, he was running root in a VM that was running as an ordinary user. What more can be done, aside from running it on a throwaway machine? Running on a cloud instance, perhaps?
- scott_karana 12y agoPerhaps a LiveCD/LiveUSB, with a VM inside of it? Then a compromise would need to be: Local VM user -> root VM user -> local LiveCD user -> root liveCD user -> hardware exploits