5 ms·
Indeed, all commonly-used hypervisors have had host escape vulnerabilities reported over the years, including Xen as used in Qubes - see e.g. http://blog.quarks
by besselheim 10y ago
Indeed, all commonly-used hypervisors have had host escape vulnerabilities reported over the years, including Xen as used in Qubes - see e.g. http://blog.quarkslab.com/xen-exploitation-part-3-xsa-182-qubes-escape.html http://blog.quarkslab.com/xen-exploitation-part-3-xsa-182-qu...
Of relevance to Edge exploitation, Microsoft are currently working on a Qubes-like sandboxing model for Edge, based on Hyper-V (though it looks like it'll be aimed towards enterprise customers rather than consumer): https://blogs.windows.com/msedgedev/2016/09/27/application-guard-microsoft-edge/#YyTRfeRwP6ihvEsb.97 https://blogs.windows.com/msedgedev/2016/09/27/application-g.... Will be interesting to see if that's part of the challenge in Pwn2Own 2018. Somewhat surprisingly, Hyper-V wasn't successfully exploited at this year's contest.
- mobiplayer 10y agoWhy are you surprised Hyper-V hasn't been exploited? Did it happen in the past? And this is VMware Workstation, not ESXi; which many people on this thread seem to be confusing.
- mzkfkkfickv 10y agoActually, the bug was in the wmware tools, which may be available on your vm's handled by esxi.
- mobiplayer 9y agoThat's not how it works I'm afraid. Otherwise if I installed those VMware tools on my physical computer and exploited them... to where do I escape? Alternate reality? :-)
- mzkfkkfickv 10y agoActually, the bug was in the wmware tools, which may be available on your vm's handled by esxi.
- besselheim 10y agoThis is the first time Hyper-V has been offered as a target in Pwn2Own, but it's had its share of host escape bugs over the years. The latest one was patched in this month's updates, just before the contest.