1 Introduction

The nefarious Dr. Evil has planted a slew of “binary bombs” on our class machines.  A binary bomb is a program that consists of a sequence of phases. Each phase expects you to type a particular string on stdin. If you type the correct string, then the phase is defused and the bomb proceeds to the next phase. Otherwise, the bomb explodes by printing "BOOM!!!" and then terminating. The bomb is defused when every phase has been defused.

There are too many bombs for us to deal with, so we are giving each student a bomb to defuse. Your mission, which you have no choice but to accept, is to defuse your bomb before the due date.  Good luck, and welcome to the bomb squad!

Step 1: Get Your Bomb

You can obtain your bomb by pointing your Web browser at:

http://proj2.eastasia.cloudapp.azure.com/

This will display a binary bomb request form for you to fill in. Enter your user name and email address and hit the Submit button.  The server will build your bomb and return it to your browser in a tar file called bombk .tar, where k is the unique number of your bomb.

The bomb will be run in the provided QEMU environment in the form of a Docker container. To set it up, simply pull the container image from ghcr .io/janssen-v/rvemu and follow the instructions on the repository: https://github.com/janssen-v/rvemuto setup your environment.

Figure 1: This is request format example.

Save the bombk .tar file to a (protected) directory in which you plan to do your work.  Then give the command:  tar  -xvf  bombk .tar.  This will create a directory called  . /bombk with the following files:

• README: Identifies the bomb and its owners.

• bomb: The executable binary bomb. (You can think of it as the .exe file)

• bomb .c: Source file with the bomb’s main routine and a friendly greeting from Dr. Evil.

The source code of everything else will be hidden from you.  You would have to defuse your bomb based on the executable file only. Before starting the lab, we recommend you to generate a full disassembly of the bomb using the command objdump  -d  bomb  >  bomb .asm. This will likely result in an assembly file of 2000+ lines.  However, do not betaken aback because most of the code are useless to your debugging process!  It will be up to you to find useful threads of clues amidst the nightmarish quagmire of tangled logic.

If for some reason you request multiple bombs, this is not a problem.  Choose one bomb to work on and delete the rest.  (but please do not order 10 bombs or sth, which might affect your score.)  Do note that every single bomb is unique.  No matter how many bombs you require, every single one has completely different answers.

Step 2: Defuse Your Bomb

Your job for this lab is to defuse your bomb.

You must run your bomb with a connection to our server, so make sure you have internet connection while you are defusing your bomb. In fact, there is a rumor that Dr.  Lethal is so lethal that the bomb will always blow up if run elsewhere.  If you submit a solution on BB without the defusal being logged on our server, we will not consider it as a valid submission. There are several other tamper-proofing devices built into the bomb as well, or so we hear.