VAGD
VirtuAlization GDb integrations in pwntools
Installation
pip install vagd
or from repo with
git clone https://github.com/gfelber/vagd
pip install ./vagd/
Usage
vagd template [OPTIONS] [BINARY] [IP] [PORT]to generate a template, list OPTIONS with help-h
from pwn import *
GOFF = 0x555555554000 # GDB default base address
IP = '' # remote IP
PORT = 0 # remote PORT
BINARY = '' # PATH to local binary
ARGS = [] # ARGS supplied to binary
ENV = {} # ENV supplied to binary
# GDB SCRIPT, executed at start of GDB session (e.g. set breakpoints here)
GDB = f"""
set follow-fork-mode parent
c"""
context.binary = exe = ELF(BINARY, checksec=False) # binary
context.aslr = False # ASLR enabled (only GDB)
vm = None
# setup vagd vm
def setup():
global vm
if args.REMOTE or args.LOCAL:
return
try:
# only load vagd if needed
from vagd import Dogd, Qegd, Box
except:
log.error('Failed to import vagd, either run locally using LOCAL or install it')
if not vm:
vm = Dogd(BINARY, image=Box.DOCKER_UBUNTU, ex=True, fast=True) # Docker
# vm = Qegd(BINARY, img=Box.QEMU_UBUNTU, ex=True, fast=True) # Qemu
if vm.is_new:
# additional setup here
log.info('new vagd instance')
# get target (pwnlib.tubes.tube)
def get_target(**kw) -> tubes.tube:
if args.REMOTE:
# context.log_level = 'debug'
return remote(IP, PORT)
if args.LOCAL:
if args.GDB:
return gdb.debug([BINARY] + ARGS, env=ENV, gdbscript=GDB, **kw)
return process([BINARY] + ARGS, env=ENV, **kw)
return vm.start(argv=ARGS, env=ENV, gdbscript=GDB, **kw)
setup()
#===========================================================
# EXPLOIT STARTS HERE
#===========================================================
# libc = ELF('', checksec=False)
t = get_target()
t.interactive() # or it()
vagd info BINARYto print info about binary
# run as process in VM
./exploit.py
# run as gdb server in VM requires tmux
./exploit.py GDB
# run on remote IP:PORT
./exploit.py REMOTE
# run process locally
./exploit.py LOCAL [GDB]
I recommend using pwndbg.
Files
All created files ares stored in the local ./.vagd/ directory. Additional large files (e.g. cloudimages) are stored in the home directory ~/.share/local/vagd/ or handled by tools themselfs (e.g. Docker).
CLI
alias vagd="python -m vagd" # or install with pip / pipx
# help message
vagd -h
# analyses the binary, prints checksec and .comment (often includes Distro and Compiler info)
vagd info BINARY
# creates template, for more info use: vagd template -h
vagd template [OPTIONS] [BINARY] [IP] [PORT]
# ssh to current vagd instance, for more info use: vagd ssh -h
vagd ssh [OPTIONS]
# scp file to/from vagd instance, for more info use: vagd scp -h
# e.g. vagd scp ./test_file vagd:./ # vagd:./ is default target
vagd scp [OPTIONS] SOURCE [TARGET]
# stop and remove current vagd instance, for more info use: vagd clean -h
vagd clean [OPTIONS]
Documentation
Boxes
A listed of known working Boxes can be found in the Documentation.
Other images might also work but currently only distributions that use apt and alpine for Docker are supported.
This limitation may be circumvented by creating a target yourself (with the dependencies gdbserver, python, openssh) and creating a ssh connection via Shgd.
Troubleshooting
background processes
all instances continue to run in the background (after a vagd object has been started), this improves the runtime greatly after the first execution of the exploit. But this means that instances must be killed manually e.g.: vagd clean
gdb & gdbserver
Because gdbserver is used to run binaries on the instances I recommend using pwndbg. Other well known gdb plugins like peda aren't compatible with gdbserver and therefore won't work.
files
files on the virtual instance are never overwritten this has performance reason (so files aren't always copied if the exploit is run). If you need to updated files on the remote either use vagd scp or create use temporary directories Dogd(..., tmp=True)
gdb performance
Using gdbserver and gdb to index libraries can be very slow. Therefore an experimental feature is available that mounts libraries locally: Dogd(..., ex=True, fast=True)
Future plans
Better Docker integration
- migrate away from ssh (attach from host) to get lower latency
- additionally virtualize containers (Qemu) in order to change the used kernel
1 maintainer
Metadata
1 maintainer
Release files for vagd 1.8.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vagd-1.8.2.tar.gz | 49.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vagd-1.8.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 103.2 kB
Release files / vagd-1.8.2.tar.gz
| Download URL | vagd-1.8.2.tar.gz |
|---|---|
| Size | 49.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbe82d0a42e4f362e95ed2a89722d138a0ddbef00b6ab47ff891710d28f27cff
|
|
BLAKE2b-256 checksum How to use checksums |
0b22bf9de488898b14e6ba57c8c627dda891071a970260a72b4b425943508b86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / vagd-1.8.2-py3-none-any.whl
| Download URL | vagd-1.8.2-py3-none-any.whl |
|---|---|
| Size | 53.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1edb2121b3b05d831def274e300eedcf09d8afd0e10610f8485a912ba4be006
|
|
BLAKE2b-256 checksum How to use checksums |
fc573d63e757c2e7b58e941a7ca6191ab0474e4291ee66b43b9a7736fadab019
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
