A tool for automating starting binary exploit challenges

• Set challenge binary to be executable
• Download a linker (ld-linux.so.*) that can segfaultlessly LD_PRELOAD the provided libc
• Download debug symbols and unstrip the libc
• Fill in a template pwntools solve script

Run pwninit

Run pwninit in a directory with the relevant files and it will detect which ones are the binary, libc, and linker. If the detection is wrong, you can specify the locations with --bin, --libc, and --ld.

If you don't like the default template, you can use your own. Just specify --template-path <path>. Check template.py for the template format. The names of the exe, libc, and ld bindings can be customized with --template-bin-name, --template-libc-name, and --template-ld-name.

You can make pwninit load your custom template automatically by adding an alias to your ~/.bashrc.

alias pwninit='pwninit --template-path ~/.config/pwninit-template.py --template-bin-name e'

Install pwninit or pwninit-bin from the AUR.

You can download non-GMO statically-linked musl binaries from the releases page.

cargo install pwninit

The binary will be placed in ~/.cargo/bin.

Note that openssl, liblzma, and pkg-config are required for the build.

$ ls
hunter  libc.so.6  readme

$ pwninit
bin: ./hunter
libc: ./libc.so.6

fetching linker
unstripping libc
setting ./ld-2.23.so executable
writing solve.py stub

$ ls
hunter  ld-2.23.so  libc.so.6  readme  solve.py

solve.py:

#!/usr/bin/env python3

from pwn import *

exe = ELF("./hunter")
libc = ELF("./libc.so.6")
ld = ELF("./ld-2.23.so")

context.binary = exe

env = dict(LD_PRELOAD="%s:%s" % (ld.path, libc.path))

def conn():
    if args.GDB:
        return gdb.debug(exe.path, env=env, gdbscript=gdbscript)
    elif args.REMOTE:
        return remote("addr", 1337)
    else:
        return process(exe.path, env=env)

gdbscript = """
continue
"""

def main():
    r = conn()

    # good luck pwning :)

    r.interactive()


if __name__ == "__main__":
    main()