SymQEMU

This is SymQEMU, a binary-only symbolic executor based on QEMU and SymCC. It currently extends QEMU 8.1 and works with the most recent version of SymCC. (See README.orig for QEMU's original README file.) A separate branch is available for the old version of SymQEMU based on QEMU 4.1.1 we don't expect much changes to happen there, but PR may be accepted.

How to build

First of all, make sure the symcc-rt submodule is initialized:

git submodule update --init --recursive subprojects/symcc-rt

Make sure that QEMU's build dependencies are installed. Most package managers provide a command to get them, e.g., apt build-dep qemu on Debian and Ubuntu, or dnf builddep qemu on Fedora and CentOS.

The following invocation is known to work on Ubuntu 22.04 and Arch:

mkdir build
cd build
../configure                                                    \
    --audio-drv-list=                                           \
    --disable-sdl                                               \
    --disable-gtk                                               \
    --disable-vte                                               \
    --disable-opengl                                            \
    --disable-virglrenderer                                     \
    --disable-werror                                            \
    --target-list=x86_64-linux-user
make -j

This will build a relatively stripped-down emulator targeting 64-bit x86 binaries. We also have experimental support for AARCH64. Working with 32-bit target architectures is possible in principle but will require a bit of work because the current implementation assumes that we can pass around host pointers in guest registers.

SymQEMU compilation options

Several compilation options are available:

enable-symcc-shared: Compile SymQEMU with the shared library of SymCC Runtime instead of a static library.
symcc-backend: Choose a specific backend from SymCC Runtime. Please have a look at symcc-rt to get an exhaustive list of available backends.

Running SymQEMU

If you built SymQEMU as described above, the binary will be in x86_64-linux-user/symqemu-x86_64. For a quick test, try the following:

$ mkdir /tmp/output
$ echo test | x86_64-linux-user/qemu-x86_64 /bin/cat -t -
This is SymCC running with the QSYM backend
[STAT] SMT: { "solving_time": 0, "total_time": 51010 }
[STAT] SMT: { "solving_time": 523 }
[INFO] New testcase: /tmp/output/000000
...

This runs your system's /bin/cat with options that make it inspect each character on standard input to check whether or not it's in the non-printable range. In /tmp/output, the default location for test cases generated by SymQEMU, you'll find versions of the input (i.e., "test") containing non-printable characters in various positions.

You can have a quick look at the results with the following one-liner:

for  i in /tmp/output/00000* ; do ; od -A x -t x1z  $i ; done

This is a very basic use of symbolic execution. See SymCC's documentation for more advanced scenarios. Since SymQEMU is based on it, it understands all the same settings, and you can even run SymQEMU with symcc_fuzzing_helper for hybrid fuzzing: just prefix the target command with x86_64-linux-user/symqemu-x86_64. (Note that you'll have to run AFL in QEMU mode by adding -Q to its command line; the fuzzing helper will automatically pick up the setting and use QEMU mode too.)

Build with Docker

Build the SymQEMU image with (this will also run the tests):

docker build -t symqemu .

You can use the docker with:

docker run -it --rm symqemu

Build with Docker Compose

Sometimes, it is more convenient to use docker-compose while developing SymQEMU, especially to avoid rebuilding for each change. It can both build symqemu and symqemu-dev.

Beware however, test the container and the host directory will be synchronized: each change in the container's source folder will be reflected on the host and vice versa (except for the build sub-folder).

A script is available to quickly get docker-compose: ./dev.sh. Alternatively the following commands can be used:

Build the symqemu-dev service:
```
docker-compose build symqemu-dev
```
Start the service:
```
docker-compose up -d symqemu-dev
```

Attach to the container:

docker-compose exec -it symqemu-dev /bin/bash

Building and testing in one line (configure only needed the first time, it is automatically rerun when needed):

docker-compose exec -it  symqemu-dev /bin/bash -c "cd build && /configure_symqemu.sh && make -j && make check"

Running SymQEMU integration tests:

docker-compose exec -it  symqemu-dev /bin/bash -c "cd /symqemu_source/tests/symqemu && python3 -m unittest test.py"

Contributing

Use the GitHub project for reporting issues, and proposing changes.

Issues

Please try to provide a minimal test case that demonstrates the problem, or ways to reproduce the behavior. If possible provide a precise line number if referring to some code. Ideally, make a PR with the test case demonstrating the failure (see next point).

Pull Requests

Pull requests are very welcome. Pull requests will only be merged if all tests pass, and ideally with a new test case to validate the correctness of the proposed modifications. QEMU tests that are not specific to SymQEMU should pass (no regression).

It is very valuable to also make a PR to add a test case for a known bug, this will facilitate correcting the issue.

Current SymQEMU tests are run by the CI from the Docker container, the following test suites are currently in place:

Unit tests: Those tests are made to validate specific instrumentation.
Integration tests: Those tests are running SymQEMU on a set of binaries and compare the results to expected results. Note that those test cases can legitimately fail if some changes are made to SymQEMU (because for example, an improvement leads to generating new test cases). In that case, update the relevant files in expected_outputs folders. It would be nice to also validate those changes with a new test case.

Also, refer to QEMU's own tests suite documentation.

Documentation

The paper contains details on how SymQEMU works. A large part of the implementation is the run-time support in accel/tcg/tcg-runtime-sym.{c,h} and accel/tcg/tcg-runtime-sym-vec.{c,h} (which delegates any actual symbolic computation to SymCC's symbolic backend), and we have modified most code-generating functions in tcg/tcg-op.c, tcg/tcg-op-vec.c and include/tcg/tcg-op-common.h to emit calls to the runtime.

For development, configure with --enable-debug for run-time assertions; there are tests for the symbolic run-time support in tests/check-sym-runtime.c.

More information about the port to QEMU 8 and internals of (Sym)QEMU can be found in the QEMU 8 merge commit message 23e570bf42 which gives some information about the adaptations performed. There are also some detailed explanations about potential problems in section 5.1 of Damien Maier's bachelor thesis.

License

SymQEMU extends the QEMU emulator and our contributions to previously existing files adopt those files' respective licenses; the files that we have added are made available under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version.

eurecom-s3 / symqemu

readme