mguarnieri/revizor

Revizor

This is Revizor, a microarchitectural fuzzer. It is an rather unconventional fuzzer as, instead of finding bugs in programs, Revizor searches for microarchitectural bugs in CPUs.

What is a microarchitectural bug? In the context of Revizor, a bug is a violation of out expectations about the CPU behaviour. The most prominent examples would be Spectre and Meltdown. Alternatively, a "bug" could also be in a form of a microarchitectural backdoor or an unknown optimization, although we are yet to encounter one of those.

See our Technical Report for details.

Origin: This is an independently developed and improved fork of SCA-Fuzzer from Microsoft.

Getting Started

Below are quick-and-dirty instructions on how to use Revizor. More detailed instructions will be added some time later.

If you find missing explanations or a bug in Revizor, don't hesitate to open an issue.

Warning: Revizor executes randomly generated code in kernel space. As you can imagine, things can go wrong. Usually they don't, but sometimes they do. So, make sure you're not running these experiments on an important machine.

0. Requirements:

   • Linux v5.6+ (tested on Linux v5.6.6-300 and v5.6.13-100; there is a good chance it will work on other versions as well, but it's not guaranteed).
   • Linux Kernel Headers
   • Python 3.7+
   • Unicorn 1.0.2+
   • PyYAML
   • For tests: Bash Automated Testing System

1. Get dependencies:

git submodule init
git submodule update
cp src/executor/x86/base.xml instruction_sets/x86

2. Install the x86 executor:

cd src/executor/x86 
sudo rmmod x86-executor
make clean
make
sudo insmod x86-executor.ko

3. Test it:

cd src/tests
./runtests.sh

If some of the "Detection" tests fail, it's fine, you might just have a slightly different microarchitecture. But if other tests fail - something is broken.

4. Fuzz it:

This one should not detect any violations and should take a few minutes to run:

cd src/
./cli.py fuzz -s instruction_sets/x86/base.xml -i 1000 -n 10 -v -c ../evaluation/1_fuzzing_main/bm-bpas.yaml

5. Find your first Spectre!

This one should detect a violations within several minutes. The detected violation is most likely an instance of Spectre V1.

cd src/
./cli.py fuzz -s instruction_sets/x86/base.xml -i 50 -n 1000 -v -c ../evaluation/fast-spectre-v1.yaml

You can find the test case that triggered this violation in src/generated.asm.

Interfaces and Architecture

Under construction