_ __ __ __ _______ ____
_ __(_)____/ /___ ______ _/ / / / / / ___// __ )
| | / / / ___/ __/ / / / __ `/ / / / / /\__ \/ __ |
| |/ / / / / /_/ /_/ / /_/ / / / /_/ /___/ / /_/ /
|_______/ \__/\__,_/\__,_/_/ \____//____/_____/
/ __/_ __________ ___ _____
/ /_/ / / /_ /_ / / _ \/ ___/
/ __/ /_/ / / /_/ /_/ __/ /
/_/ \__,_/ /___/___/\___/_/
A KVM/QEMU based USB-fuzzing framework.
Sergej Schumilo, OpenSource Security Spenneberg 2015
Version: 0.2
A USB-fuzzer which takes advantage of massive usage of virtual machines and also offers high reproducibility. This framework was initially released at Black Hat Europe 2014.
This software is under heavy development. Get a copy of the actual version at github:
This software is licensed under GPLv2.
This framework provides:
- USB-fuzzing in practical time frames
- multiprocessing and clustering
- export sequences of payloads and replay them for debugging or investigation
- XML-based dynamic testcase generating
- expandable by writing new testcases, USB-emulators or monitoring-modules
vUSBf was written in python2 and requires the Scapy-framework.
First of all we've to build a compatible version of QEMU! Get the newest version of QEMU and usbredir:
QEMU: http://www.qemu.org usbredir: https://github.com/SPICE/usbredir
Be sure that you compile QEMU with the option "usb_redir" and you also patch the file /hw/usb/redirection.c. If you're using the QEMU version 2.1.1, you can apply our patch (qemu-2.1.1.patch). QEMU 2.2.x is currently unsupported by vUSBf!
vUSBf requires some prepared QCOW2-images for fuzzing! At first you've to create a QCOW2-image for your virtual machine. You can do this by using the following command:
qemu-img create -f qcow2 vm.qcow2 10G
Install your preferred operating system on that image. You've to configure a TTY which is available at the (virtual) serial port.
The next step is to create a backing-file (overlay which contains all of the future delta) and an image which will contain a snapshot of the VM (the size should be larger than your virtual memory you have configured):
qemu-img create -b vm.img -f qcow2 overlay.qcow2
qemu-img create -f qcow2 ram.qcow2 1G
Start your VM with the following command, wait until the kernel is loaded, log in and change the verbosity of printk by entering "echo '7' > /proc/sys/kernel/printk". Now you can take a snapshot by entering the QEMU console (press ctrl+a and c) and type savevm . You should start the VM by the following command:
qemu-system-x86_64 --enable-kvm -m 1024 -hdb ram.qcow2 -hda overlay.qcow2 -serial mon:stdio -device nec-usb-xhci -device usb-redir,chardev=usbchardev,debug=0 -chardev socket,server,id=usbchardev,nowait,host=127.0.0.1,port=1336
Create a customized configuration in the "vusbf/configurations/" folder. You'll find there some examples. Modify the following information:
- location of your QEMU-binary you want to use
- KVM support (write yes or no)
- size of your memory (the unit is MB)
- location of your ram-file
- location of your overlay-file
- location where your overlay duplicates should be stored
- configured USB-host-controller (if you have no idea just write nec-usb-xhci)
- some extra parameters for QEMU (if you need some)
- the name of the snapshot
That's all. Now your VM is ready for some fuzzing.
Take a look at help.txt or run vusbf with the parameter -h for help :-)
There are some known bugs like the buggy support for Windows systems. We are working on these issues, so be sure you are using the newest version. Moreover the lack of USB-emulators is another point we are working on.
Furthermore some inline comments have been written in my native language (german). They will be translated later ;-) and the code will be more documented!
Comrade-in-arms are welcome :-)! There is a lot of work to do!
Feel free to send us an email: schumilo@fh-muenster.de info@os-t.net
