The ELF Virus Writing HOWTO: sparc-debian2.2-linux
Prev |  | Next

# 2. The magic of the Elf

| Any sufficiently advanced technology is indistinguishable from magic.
| Arthur C. Clarke

For the first example I'll present the simplest piece of code that still gives sufficient feedback. Our aim is to implant it into `/bin/sh`. On practically every recent installation of Linux/sparc the following code will emit three magic letters instead of just dumping core.

Source: pre/sparc-debian2.2-linux/magic_elf/magic_elf.c

    #include <unistd.h>
    int main() { write(1, (void*)0x10001, 3); return 0; }

Command: pre/sparc-debian2.2-linux/magic_elf/cc.sh

    #!/bin/sh
    /usr/bin/gcc -O1 -I out/sparc-debian2.2-linux -D NDEBUG \
    	pre/sparc-debian2.2-linux/magic_elf/magic_elf.c \
    	-o tmp/sparc-debian2.2-linux/magic_elf/magic_elf \
    && tmp/sparc-debian2.2-linux/magic_elf/magic_elf

Output: out/sparc-debian2.2-linux/magic_elf/magic_elf

    ELF

## 2.1. How it works

### 2.1.1. Digested answer

The three letters are part of the signature of ELF files. Executables created by ld(1) are always mapped into the same memory region. That's why the program can find its own header at a predictable virtual address.

### 2.1.2. Short answer

RTFM. [1] Just read all of Executable and linkable format.

### 2.1.3. Sort of an answer

`0x10000` is not a natural constant, but happens to be the default base address of ELF executables produced by ld(1) on sparc. Option `-Ttext ORG` and `--section-start SECTIONNAME=ORG` of `GNU ld` should allow to change it, but I didn't get it working. Anyway, the layout of executables produced by ld(1) is straight forward.

1. One ELF header - Elf32_Ehdr

2. Program headers - Elf32_Phdr

3. Program interpreter (not if statically linked)

4. Code

5. Data

6. Section headers - Elf32_Shdr

Everything from the start of the file to the last byte of code is mapped into one segment (colloquially named "code" or "text") that begins at the base address. There is a whole chapter called readelf & objdump describing tools to view all these details. In the meantime I will show fancy ways to get by without.

## 2.2. Strings and dumps

What would you do if you knew nothing about ELF and just asked yourself how that example works? How can you go sure that the executable file really contains those three letters?

### 2.2.1. strings

A good start for finding text in binary files is strings(1).

Command: pre/sparc-debian2.2-linux/magic_elf/strings.sh

    #!/bin/sh
    # without "-a -n 3" we don't get any output
    /usr/bin/strings -a -n 3 tmp/sparc-debian2.2-linux/magic_elf/magic_elf \
    | /bin/grep -n ELF

Output: out/sparc-debian2.2-linux/magic_elf/strings

    1:ELF

The leading `1:` is written by grep(1) and tells that our three-letter word is the first found string. This gives some help where we can find it in a hex dump. It is difficult to search strings in such a dump because of line breaks. Interactive tools like hexedit(1) or khexedit(1) might be useful.

### 2.2.2. od

The traditional tool for dumps is called od(1), the abbreviation for "octal dump". The classic version does provide hexadecimal output, but unfortunately not for single bytes. Option `-x` outputs "words", which are defined to be two bytes. This does not matter on big-endian machines like the sparc, but on i386 and alpha it is quite confusing.

On both Linux and SunOS `od` features option `-tx1` to get byte-wise hexadecimals. FreeBSD's `od` has no equivalent. Another interesting option is `-N count` which reads no more than `count` bytes of input. Again it is not available on FreeBSD.

Command: pre/sparc-debian2.2-linux/magic_elf/od/Linux.sh

    #!/bin/sh
    src=tmp/sparc-debian2.2-linux/magic_elf/magic_elf
    /usr/bin/od -N 16 -c   ${src} | /usr/bin/head -1
    /usr/bin/od -N 16 -x   ${src} | /usr/bin/head -1
    /usr/bin/od -N 16 -tx1 ${src} | /usr/bin/head -1
    /usr/bin/od -N 16 -ta  ${src} | /usr/bin/head -1

Output: out/sparc-debian2.2-linux/magic_elf/od

    0000000 177   E   L   F 001 002 001  \0  \0  \0  \0  \0  \0  \0  \0  \0
    0000000 7f45 4c46 0102 0100 0000 0000 0000 0000
    0000000 7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00
    0000000 del   E   L   F soh stx soh nul nul nul nul nul nul nul nul nul

### 2.2.3. hexdump

`hexdump` features user defined formats. It is a typical ingredient of Linux and FreeBSD installations, but not shipped with SunOS.

Source: pre/sparc-debian2.2-linux/format.hex

    "%04.4_ax  " 8/1 "%02x " "  " 8/1 "%02x "
    "  " 16/1 "%_p" "\n"

Source: pre/sparc-debian2.2-linux/magic_elf/hexdump.sh

    #!/bin/sh
    /usr/bin/hexdump -n 80 -f pre/sparc-debian2.2-linux/format.hex \
    < tmp/sparc-debian2.2-linux/magic_elf/magic_elf

Output: out/sparc-debian2.2-linux/magic_elf/hexdump

    0000  7f 45 4c 46 01 02 01 00  00 00 00 00 00 00 00 00  .ELF............
    0010  00 02 00 02 00 00 00 01  00 01 06 30 00 00 00 34  ...........0...4
    0020  00 00 1c 94 00 00 00 00  00 34 00 20 00 06 00 28  .........4. ...(
    0030  00 1b 00 18 00 00 00 06  00 00 00 34 00 01 00 34  ...........4...4
    0040  00 01 00 34 00 00 00 c0  00 00 00 c0 00 00 00 05  ...4............

### 2.2.4. xxd

`xxd` is part of `vim`. [2] And though that can't be called installation core it comes pretty close on Linux distributions.

Source: pre/sparc-debian2.2-linux/magic_elf/xxd.sh

    #!/bin/sh
    /usr/bin/xxd -l 80 \
    < tmp/sparc-debian2.2-linux/magic_elf/magic_elf

Output: out/sparc-debian2.2-linux/magic_elf/xxd

    0000000: 7f45 4c46 0102 0100 0000 0000 0000 0000  .ELF............
    0000010: 0002 0002 0000 0001 0001 0630 0000 0034  ...........0...4
    0000020: 0000 1c94 0000 0000 0034 0020 0006 0028  .........4. ...(
    0000030: 001b 0018 0000 0006 0000 0034 0001 0034  ...........4...4
    0000040: 0001 0034 0000 00c0 0000 00c0 0000 0005  ...4............

Anyway, at this point we can guess that file offset 1 and `0x10000 + 1` are not coincidental. A test program might help.

## 2.3. The address of main

Source: pre/sparc-debian2.2-linux/magic_elf/addr_of_main.c

    #include <stdio.h>

    int main()
    {
      printf("# sizeof(unsigned long)=%u\n", (unsigned)sizeof(unsigned long));
      printf("# 10000=%#02x\n", *(unsigned char*)0x10000);
      printf("# 10001=%.3s\n", (char*)0x10001);
      printf("main_p=%p\n", main);
      printf("main_l=%lx\n", (unsigned long)main);
      printf("ofs=%lu\n", (unsigned long)main - 0x10000);
      return 0;
    }

Output: out/sparc-debian2.2-linux/magic_elf/addr_of_main

    # sizeof(unsigned long)=4
    # 10000=0x7f
    # 10001=ELF
    main_p=0x1073c
    main_l=1073c
    ofs=1852

Note that the output of `%p` is not standardized. Some platforms print a leading `0x`, some don't. Even `%#p` does not guarantee a leading `0x`. Anyway, output looks good. The byte at address `0x10000 + 0` is equal to that at file offset 0. And 0x1073c is a plausible address of function `main`.

## 2.4. Other roads to ELF

Source: pre/sparc-debian2.2-linux/magic_elf/other_perl.pl

    #!/usr/bin/perl -w
    syscall 4, 1, 0x10001, 3

Output: out/sparc-debian2.2-linux/magic_elf/other_perl

    ELF

Source: pre/sparc-debian2.2-linux/magic_elf/other_exe.sh

    #!/bin/sh
    /bin/dd if=/proc/self/exe bs=1 skip=1 count=3 2>/dev/null

Output: out/sparc-debian2.2-linux/magic_elf/other_exe

    ELF

Command: pre/sparc-debian2.2-linux/magic_elf/other_mem.sh

    #!/bin/sh
    skip=$( echo "ibase=16; 10001" | /usr/bin/bc )
    /bin/dd if=/proc/self/mem bs=1 skip=${skip} count=3 2>/dev/null

Output: out/sparc-debian2.2-linux/magic_elf/other_mem

    ELF

### Notes

[1] | http://www.tuxedo.org/~esr/jargon/html/entry/RTFM.html
[2] | http://www.vim.org

Prev | Home | Next
Variables & packages |  | Magic revealed