Windows 10: Fuzzing para-virtualized devices in Hyper-V

Brink · Jan 28, 2019

Hyper-V is the backbone of Azure, running on its Hosts to provide efficient and fair sharing of resources, but also isolation. That’s why we, in the vulnerability research team for Windows, have been working in the background for years now helping secure Hyper-V. And why Microsoft invites security researchers across the globe to submit their vulnerabilities through the Hyper-V Bounty Program for payment of up to $250,000 USD.

To help engage people in the Hyper-V security space, last year internal teams from Microsoft published some of their work.

At BlackHat 2018 USA Joe Bialek and Nicolas Joly presented "A Dive in to Hyper-V Architecture and Vulnerabilities". They covered an architecture overview of Hyper-V oriented to security researchers. They also discussed some interesting vulnerabilities seen in Hyper-V.

In the same conference, Jordan Rabet presented "Hardening Hyper-V through offensive security research", where he discussed in great detail the exploitation process for CVE-2017-0075 in VMSwitch, a Hyper-V component.

Last December Saar Amar published a detailed blog with the fundamentals to get introduced into Hyper-V security research.

Following their work, we’d like to share a new story related to Hyper-V security for anyone interested in getting introduced in Hyper-V security or learning more. Recently we have been working in Virtual PCI (VPCI), one of the para-virtualized devices available in Hyper-V, used to expose hardware to virtual machines. As other para-virtualized devices, it uses VMBus for inter-partition communication.

On this blog we would like to share some of our learnings, introduce both VMBus and VPCI, share one strategy to fuzz the VMBus channel used by VPCI and discuss one of our findings. Some of the concepts and strategies here can be used to work with other virtual devices using VMBus in Hyper-V...
Click to expand...

Read more: Fuzzing para-virtualized devices in Hyper-V Defense

:)

Mark St... · Jan 28, 2019

Hyper V not connecting to virtual machine

Hi.

Regarding Hyper V firstly check all steps and requirements from here:

https://docs.microsoft.com/en-us/virtualization...

And here

https://docs.microsoft.com/en-us/virtualization...

For more details about how to set up it better to use another community:

https://social.technet.microsoft.com/Forums/en-...

Rex99ny · Jan 28, 2019

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

In Hyper-V Manager, click Action > New >
Virtual Machine to bring up the New

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?

jbl1985 · Jan 28, 2019

Importing Virtual PC -> Hyper V

Thank you. I followed the instructions below, and when I go to hit the action menu to install Integration services, of course, there is no such option under the Action Menu. The instructions seem so simple but I'm still missing something...

Step 4: Install or upgrade integration services

Hyper-V includes a software package for supported guest operating systems that improves integration between the physical computer and the virtual machine. This package is referred to as integration services. To learn more, see Integration
Services.

This step can't be automated or done within a Windows PowerShell session.

To install integration services

Open Hyper-V Manager. From the Server Manager Tools menu, click Hyper-V Manager.

Connect to the virtual machine. Right-click the name of the virtual machine and click Connect.

From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. This action loads the setup disk in the virtual DVD drive. Depending on the guest operating system installed, you may
need to start the installation manually.

After the installation finishes, all integration services are available for use.

Windows 10: Fuzzing para-virtualized devices in Hyper-V

Fuzzing para-virtualized devices in Hyper-V

Fuzzing para-virtualized devices in Hyper-V

Fuzzing para-virtualized devices in Hyper-V

Fuzzing para-virtualized devices in Hyper-V - Similar Threads - Fuzzing para virtualized

Can't Create Hyper-V VM and Hyper-V Virtual Switch

Backing up Hyper-V Virtual Machines

Virtual network is not created in Hyper-V

Virtual Hard disk created in hyper-v

Hyper-v virtual switch breaks my network

Hyper-V Virtual Switch

Import Hyper-V Virtual Machine in Windows 10

Export Hyper-V Virtual Machine in Windows 10

Create Shortcut of Hyper-V Virtual Machine in Windows