PluginBench
Skill
Review
Audit score 70

symbolic-execution-tools

yaklang/hack-skills

Symbolic execution and constraint solving for CTF reversing, key recovery, and binary analysis with angr, Z3, and Unicorn.

What is symbolic-execution-tools?

Expert playbook for symbolic execution techniques using angr, Z3, and Unicorn Engine. Use this skill when solving CTF reversing challenges, recovering cryptographic keys, bypassing security checks, or automating binary analysis. Covers constraint solving patterns, function hooking, state initialization, and emulation-based unpacking.

  • Symbolic execution of binaries with angr to explore control flow paths and solve constraints automatically
  • Constraint solving with Z3 for pure mathematical problems, key recovery, and equation systems
  • Fast code emulation with Unicorn Engine for unpacking, decryption, and isolated function analysis
  • Function hooking and SimProcedure replacement to bypass libc calls and custom checks
  • Symbolic stdin/argv/file input patterns for automated challenge solving
  • Memory and register manipulation with symbolic-aware operations

How to install symbolic-execution-tools

npx skills add https://github.com/yaklang/hack-skills --skill symbolic-execution-tools
Prerequisites
  • Python 3.7+
  • angr, claripy, Z3, and Unicorn Engine installed (pip install angr z3-solver unicorn capstone)
  • Basic understanding of x86/x64 assembly and binary analysis
  • Familiarity with constraint solving concepts
Claude Code
Cursor
Windsurf
Cline

How to use symbolic-execution-tools

  1. 1.Install the skill and load ANGR_COOKBOOK.md for ready-to-use script patterns
  2. 2.Create a Project object pointing to your binary and initialize a state (entry_state, blank_state, or full_init_state)
  3. 3.Define symbolic variables using claripy.BVS() for inputs you want to solve for
  4. 4.Add constraints to the solver (state.solver.add) to guide exploration toward the goal
  5. 5.Use simgr.explore(find=target, avoid=bad) to automatically find paths that satisfy your conditions
  6. 6.Extract the solution by evaluating symbolic variables: state.solver.eval(sym_var, cast_to=bytes)
  7. 7.For pure math problems, use Z3 directly with BitVec and Solver instead of angr
  8. 8.For isolated code regions, use Unicorn Engine to emulate without symbolic overhead

Use cases

Good for
  • Automating CTF reversing challenges by symbolically exploring paths to find valid inputs
  • Recovering encryption keys or serial numbers by setting up constraint systems
  • Unpacking and decrypting obfuscated code regions using Unicorn emulation
  • Bypassing anti-debugging or validation checks through symbolic state manipulation
  • Analyzing custom VM bytecode or firmware code by combining angr with Unicorn
Who it's for
  • CTF competitors and reverse engineers
  • Security researchers analyzing malware or firmware
  • Binary analysis automation engineers
  • Exploit developers needing to recover keys or bypass checks

symbolic-execution-tools FAQ

When should I use angr vs Z3 vs Unicorn?

Use Z3 for pure constraint systems without binary code. Use angr when you need to explore binary control flow and manage constraints automatically. Use Unicorn for fast emulation of specific code regions without symbolic overhead. Combine angr + Unicorn for complex binaries with custom VMs.

Why does my angr script produce broken results?

Common issues: incorrect state initialization (use full_init_state for argc/argv), missing hooks for libc functions (printf, scanf, strcmp), or path explosion from unconstrained loops. Use the ANGR_COOKBOOK.md patterns and add hooks for problematic functions.

How do I handle symbolic stdin in angr?

Create a symbolic bitvector with claripy.BVS(), pass it to entry_state(stdin=sym_stdin), then add byte-range constraints (0x20-0x7e for printable ASCII) to guide the solver.

Can I use angr for firmware or kernel code?

angr works for user-space binaries. For kernel/firmware, use Qiling which provides full system emulation with OS awareness. For isolated firmware routines, Unicorn Engine is faster.

How do I avoid path explosion in angr?

Use avoid= to prune bad paths, add aggressive constraints early, limit exploration depth, or use Unicorn for known code regions instead of symbolic execution.

Full instructions (SKILL.md)

Source of truth, from yaklang/hack-skills.


name: symbolic-execution-tools description: >- Symbolic execution and constraint solving playbook. Use when solving CTF reversing challenges, recovering keys, bypassing checks, or automating binary analysis with angr, Z3, or Unicorn Engine.

SKILL: Symbolic Execution Tools — Expert Analysis Playbook

AI LOAD INSTRUCTION: Expert symbolic execution techniques using angr, Z3, and Unicorn Engine. Covers CTF challenge automation, constraint solving patterns, function hooking, SimProcedure replacement, and emulation-based unpacking. Base models often produce broken angr scripts due to incorrect state initialization or missing hooks for libc functions.

0. RELATED ROUTING

  • anti-debugging-techniques when anti-debug checks need to be symbolically bypassed
  • code-obfuscation-deobfuscation when using symbolic execution for deobfuscation
  • vm-and-bytecode-reverse when applying angr to custom VM challenges

Advanced Reference

Also load ANGR_COOKBOOK.md when you need:

  • 15+ ready-to-use angr script patterns for common CTF challenges
  • Hook templates for scanf, printf, malloc, strcmp
  • Symbolic file input, stdin, argv patterns
  • Optimization tricks for path explosion management

When to use which tool

ScenarioBest ToolWhy
Pure math / equation systemZ3Direct constraint solving, no binary needed
Binary with control flowangrExplores paths, manages constraints automatically
Emulate specific code regionUnicornFast, no symbolic overhead, good for unpacking
Complex binary + custom VMangr + Unicorn (combo)angr for control flow, Unicorn for VM handlers
Kernel / firmware codeQilingFull system emulation with OS awareness

1. ANGR — CORE CONCEPTS

1.1 Pipeline

Project(binary)
  → Factory.entry_state() / blank_state(addr=)
    → SimulationManager(state)
      → explore(find=target, avoid=bad)
        → found[0].solver.eval(symbolic_var)

1.2 Essential Setup

import angr
import claripy

proj = angr.Project('./challenge', auto_load_libs=False)

# Entry state: start from program entry point
state = proj.factory.entry_state()

# Blank state: start from arbitrary address
state = proj.factory.blank_state(addr=0x401000)

# Full init state: with command-line args
state = proj.factory.full_init_state(args=['./challenge', arg1_sym])

simgr = proj.factory.simulation_manager(state)
simgr.explore(find=0x401234, avoid=[0x401300])

if simgr.found:
    found = simgr.found[0]
    solution = found.solver.eval(symbolic_input, cast_to=bytes)
    print(f"Solution: {solution}")

1.3 Symbolic Variables (claripy)

# Bitvector (fixed-size integer)
sym_input = claripy.BVS("input", 64)        # 64-bit symbolic
sym_byte = claripy.BVS("byte", 8)           # 8-bit symbolic
sym_buf = claripy.BVS("buffer", 8 * 32)     # 32-byte buffer

# Concrete bitvector
concrete = claripy.BVV(0x41, 8)             # concrete value 0x41

# Constraints
state.solver.add(sym_input > 0)
state.solver.add(sym_input < 100)
state.solver.add(sym_byte >= 0x20)           # printable ASCII
state.solver.add(sym_byte <= 0x7e)

# Evaluate
value = state.solver.eval(sym_input)
all_values = state.solver.eval_upto(sym_input, 10)  # up to 10 solutions

1.4 Symbolic stdin

flag_len = 32
sym_stdin = claripy.BVS("stdin", 8 * flag_len)

state = proj.factory.entry_state(stdin=sym_stdin)

# Constrain to printable ASCII
for i in range(flag_len):
    byte = sym_stdin.get_byte(i)
    state.solver.add(byte >= 0x20)
    state.solver.add(byte <= 0x7e)

1.5 Hooking Functions

# Hook by address (skip N bytes of original code)
@proj.hook(0x401100, length=5)
def skip_check(state):
    state.regs.eax = 1  # force success

# SimProcedure: replace library function
class MyStrcmp(angr.SimProcedure):
    def run(self, s1, s2):
        return claripy.If(
            self.state.memory.load(s1, 32) == self.state.memory.load(s2, 32),
            claripy.BVV(0, 32),
            claripy.BVV(1, 32)
        )

proj.hook_symbol('strcmp', MyStrcmp())

# Hook common problematic functions
proj.hook_symbol('printf', angr.SIM_PROCEDURES['libc']['printf']())
proj.hook_symbol('scanf', angr.SIM_PROCEDURES['libc']['scanf']())
proj.hook_symbol('puts', angr.SIM_PROCEDURES['libc']['puts']())

1.6 Memory Operations

# Read memory (symbolic-aware)
data = state.memory.load(addr, size)          # returns BV
data_concrete = state.solver.eval(data, cast_to=bytes)

# Write memory
state.memory.store(addr, claripy.BVV(0x41, 8))
state.memory.store(addr, sym_buf)

# Read/write registers
rax = state.regs.rax
state.regs.rdi = claripy.BVV(0x1000, 64)

2. Z3 CONSTRAINT SOLVING

2.1 Core API

from z3 import *

# Sorts
x = BitVec('x', 32)    # 32-bit bitvector
y = Int('y')             # arbitrary precision integer
b = Bool('b')            # boolean

# Solver
s = Solver()
s.add(x + y == 42)
s.add(x > 0)
s.add(y > 0)

if s.check() == sat:
    m = s.model()
    print(f"x = {m[x]}, y = {m[y]}")

2.2 Common CTF Patterns

# Serial key validation: each char satisfies constraints
key = [BitVec(f'k{i}', 8) for i in range(16)]
s = Solver()
for k in key:
    s.add(k >= 0x30, k <= 0x7a)  # alphanumeric-ish

# XOR key recovery
plaintext = b"known_plaintext"
ciphertext = b"\x12\x34..."
key_byte = BitVec('key', 8)
s = Solver()
for p, c in zip(plaintext, ciphertext):
    s.add(p ^ key_byte == c)

# System of linear equations (modular)
a, b, c = BitVecs('a b c', 32)
s = Solver()
s.add(3*a + 5*b + 7*c == 0x12345678)
s.add(2*a + 4*b + 6*c == 0xDEADBEEF)
s.add(a ^ b ^ c == 0xCAFEBABE)

2.3 Optimization

from z3 import Optimize

opt = Optimize()
x = BitVec('x', 32)
opt.add(x > 0)
opt.add(x < 1000)
opt.minimize(x)  # find smallest satisfying value
opt.check()
print(opt.model())

3. UNICORN ENGINE — CODE EMULATION

3.1 Basic Setup

from unicorn import *
from unicorn.x86_const import *
from capstone import Cs, CS_ARCH_X86, CS_MODE_64

mu = Uc(UC_ARCH_X86, UC_MODE_64)

CODE_ADDR = 0x400000
STACK_ADDR = 0x7fff0000
STACK_SIZE = 0x10000

mu.mem_map(CODE_ADDR, 0x10000)
mu.mem_map(STACK_ADDR, STACK_SIZE)

mu.mem_write(CODE_ADDR, code_bytes)
mu.reg_write(UC_X86_REG_RSP, STACK_ADDR + STACK_SIZE - 0x1000)
mu.reg_write(UC_X86_REG_RBP, STACK_ADDR + STACK_SIZE - 0x1000)

mu.emu_start(CODE_ADDR, CODE_ADDR + len(code_bytes))

result = mu.reg_read(UC_X86_REG_RAX)

3.2 Hooking Memory & Instructions

# Hook memory access
def hook_mem(uc, access, address, size, value, user_data):
    if access == UC_MEM_WRITE:
        print(f"Write {value:#x} to {address:#x}")
    elif access == UC_MEM_READ:
        print(f"Read from {address:#x}")

mu.hook_add(UC_HOOK_MEM_READ | UC_HOOK_MEM_WRITE, hook_mem)

# Hook specific instruction (for tracing)
def hook_code(uc, address, size, user_data):
    code = uc.mem_read(address, size)
    md = Cs(CS_ARCH_X86, CS_MODE_64)
    for insn in md.disasm(bytes(code), address):
        print(f"  {insn.address:#x}: {insn.mnemonic} {insn.op_str}")

mu.hook_add(UC_HOOK_CODE, hook_code)

3.3 Use Cases

Use CaseApproach
Unpack shellcodeMap shellcode, emulate, dump decoded payload
Decrypt stringsEmulate decryption function with controlled inputs
Brute-force short keysLoop emulation with different key inputs
Analyze obfuscated functionEmulate function, observe register/memory state
Firmware code emulationMap firmware memory layout, emulate routines

4. ANGR EXPLORATION STRATEGIES

4.1 find/avoid

simgr.explore(
    find=lambda s: b"Correct" in s.posix.dumps(1),   # stdout contains "Correct"
    avoid=lambda s: b"Wrong" in s.posix.dumps(1)      # avoid "Wrong" output
)

4.2 Managing Path Explosion

StrategyImplementation
Constrain input spaceAdd constraints (printable, length limits)
Avoid dead-end pathsUse avoid= for known failure addresses
Hook complex functionsReplace with simplified SimProcedure
Limit loop iterationsstate.options.add(angr.options.LAZY_SOLVES)
Use veritestingsimgr.explore(..., technique=angr.exploration_techniques.Veritesting())
DFS instead of BFSsimgr.use_technique(angr.exploration_techniques.DFS())
Timeout per pathsimgr.explore(..., num_find=1) + timeout wrapper

4.3 Concrete + Symbolic Hybrid

state = proj.factory.entry_state(
    add_options={angr.options.UNICORN}  # use Unicorn for concrete regions
)

This dramatically speeds up execution: concrete code runs natively via Unicorn, switching to symbolic only when symbolic variables are involved.


5. PRACTICAL WORKFLOW

5.1 CTF Binary Solving Workflow

1. Static analysis: identify input method, success/fail conditions
   └─ Find "Correct" / "Wrong" strings → get their xref addresses

2. Choose tool:
   ├─ Pure math (no binary needed) → Z3
   ├─ Small binary, clear success/fail → angr explore
   └─ Specific function to emulate → Unicorn

3. Set up symbolic input:
   ├─ stdin → claripy.BVS + entry_state(stdin=)
   ├─ argv → full_init_state(args=[...])
   ├─ file input → SimFile
   └─ specific memory → state.memory.store(addr, sym)

4. Hook problematic functions:
   ├─ printf/puts → SimProcedure or no-op
   ├─ scanf → custom handler
   ├─ time/random → return concrete value
   └─ anti-debug → skip entirely

5. Explore and extract:
   └─ simgr.explore(find=, avoid=) → solver.eval()

6. DECISION TREE

Need to solve a reversing challenge?
│
├─ Is the challenge pure math / equations?
│  └─ Yes → Z3
│     ├─ Linear equations → BitVec + Solver
│     ├─ Modular arithmetic → BitVec (natural mod 2^n)
│     ├─ Boolean logic → Bool + Solver
│     └─ Optimization → Optimize + minimize/maximize
│
├─ Is it a compiled binary with clear success/fail?
│  └─ Yes → angr
│     ├─ Input via stdin → symbolic stdin
│     ├─ Input via argv → full_init_state with symbolic args
│     ├─ Input via file → SimFile
│     ├─ Path explosion → add constraints, avoid paths, hook loops
│     └─ Complex library calls → hook with SimProcedure
│
├─ Need to emulate a specific function/region?
│  └─ Yes → Unicorn Engine
│     ├─ Decryption routine → map code + data, emulate, read result
│     ├─ Shellcode analysis → map shellcode, hook syscalls
│     └─ Key schedule → emulate with different inputs
│
├─ Need to analyze firmware / exotic arch?
│  └─ Yes → Qiling (full system emulation with OS support)
│
├─ Binary has VM protection?
│  └─ angr for handler analysis + Z3 for bytecode constraints
│
└─ None of the above working?
   ├─ Combine: Unicorn for concrete regions + Z3 for constraints
   ├─ Manual reverse engineering with debugger
   └─ Side-channel approach (timing, power analysis for hardware)

7. COMMON PITFALLS & FIXES

ProblemCauseFix
angr hangs foreverPath explosion in loopsAdd avoid= for loop-back edges, or hook the loop
Z3 returns unknownNon-linear constraints too complexSimplify, split into sub-problems, use set_param("timeout", 5000)
Unicorn crashes on syscallSyscall not handledHook syscall interrupt, handle or skip
angr wrong resultIncorrect state initializationVerify initial memory layout matches actual binary
Symbolic memory too largeUnbounded symbolic readsConcretize array indices where possible
SimProcedure wrong typesArgument type mismatchCheck calling convention (cdecl vs fastcall)
angr can't load binaryMissing librariesUse auto_load_libs=False + hook needed symbols

8. TOOL VERSIONS & INSTALLATION

# angr (Python 3.8+)
pip install angr

# Z3
pip install z3-solver

# Unicorn Engine
pip install unicorn

# Capstone (disassembly, pairs with Unicorn)
pip install capstone

# Keystone (assembly)
pip install keystone-engine