Skip to content
Automatically exported from code.google.com/p/hyperdbg
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
core Added a proper event for EPT violations. Jun 14, 2014
docs
hyperdbg
libudis86
Kbuild
Makefile.linux
Makefile.windows

README

HyperDbg is a kernel debugger that leverages hardware-assisted
virtualization. More precisely, HyperDbg is based on a minimalistic hypervisor
that is installed while the system runs. Compared to traditional kernel
debuggers (e.g., WinDbg, SoftIce, Rasta R0 Debugger) HyperDbg is completely
transparent to the kernel and can be used to debug kernel code without the need
of serial (or USB) cables. For example, HyperDbg allows to single step the
execution of the kernel, even when the kernel is executing exception and
interrupt handlers. Compared to traditional virtual machine based debuggers
(e.g., the VMware builtin debugger), HyperDbg does not require the kernel to be
run as a guest of a virtual machine, although it is as powerful.

Once loaded, the debugger will sits in background and will pop up the GUI when
the F12 hot-key is pressed or when a debug event occurs. 

The current version of HyperDbg is a prototype and will evolve drastically in
the future. Currently the debugger allows to set breakpoints, to single step
the execution of the kernel, to inspect the memory of the operating system and
of a particular process. However, the debugger currently does not distinguish
between threads, has limited support for kernel's symbols, and has does not
clone shared pages before setting a breakpoint. Future version of the debugger
will be based on an enhanced version of the hypervisor that guarantees complete
isolation and transparency.

HyperDbg currently only supports:

 * systems with PS/2 keyboards
 * systems with Intel VT-x
 * systems running 32-bit OSes and applications (no PAE)
 * Windows XP (SP2).

HyperDbg renders the GUI by writing directly to the memory of the video
card. Some video cards are known to give problems. The debugger does not work
correctly when the accelerated drivers for the following cards are loaded:

 * Intel 82915g 
 * nvidia GeForce 9800GT
 * nvidia GeForce GT 130

If you have any of the aforementioned cards (and you are using the accelerated
driver) or if the interface is not correctly rendered on the screen, you have
to disable the driver in order to be able to use HyperDbg. The driver used by
default by Windows XP does not give any problem.

See the file INSTALL for compilation instructions. 

HyperDbg is developed by:

 * Aristide Fattori    <joystick@security.dico.unimi.it>
 * Lorenzo Martignoni  <martignlo@gmail.com>
 * Roberto Paleari     <roberto.paleari@gmail.com>

Comments, suggestions, criticisms, and patches are very welcome and can be sent
by email to the authors.

You can’t perform that action at this time.