Virtual box 3D Acceleration OpenGL Host escape #3634
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Module for vulnerability discussed here: http://corelabs.coresecurity.com/index.php?module=Wiki&action=view&type=publication&name=oracle_virtualbox_3d_acceleration
And exploitation discussed here: http://www.vupen.com/blog/20140725.Advanced_Exploitation_VirtualBox_VM_Escape.php
At the moment this module doesn't add the CoE proposed by VUPEN, even when it looks feasible from the description. With the actual payload system, looks like the place to add the post-exploitation code to fix the corrupted process should be by adding the stub as "Append". Unfortunately, the Append stub code only will be reached when the user "exit" from the achieved meterpreter. Using migrate as initial script doesn't help, since the original process will crash before reaching the "Append" stub, so there is no opportunity to restore the process. Modifying the current payload system is out of the scope of this pull request atm, but definitely would like to look into it. Feedback is welcome!
Also, even without the CoE code proposed by VUPEN, by just "fixing" the stack, things are not "so busted" and the guest will continue executing unless other code tries to use the '.\VBoxGuest' device. Even with it, I've marked
Rank
asAverageRanking
. I don't mind to lower it even more if anyone thinks it should be done. The session can be executed and even exited in the Host system, and both the host and guest keep running on my tests (Unless the Guest tries to access the named device of course, in this case the Guest probably will die :-( )