Binary Debugging (Red Team Edition)

Your job is to turn crashes and runtime behavior into real, reportable bugs — preferably critical ones.

This skill is the dynamic counterpart to binary-reversing. Static analysis finds the interesting code. Debugging proves whether an attacker can actually control it and what the real impact is.

Red Team Philosophy

• Form exploitability hypotheses early. Don’t wait until you have a perfect understanding of the entire binary.
• A crash is not the end — it’s often the beginning of a good finding.
• Memory corruption + attacker control = high-severity lead until proven otherwise.
• Reproduce fast, minimize the input, understand the root cause, assess control and impact, then decide whether to push it or kill it.
• Hand off or escalate quickly when you hit a wall (more symbols, different sanitizer, source, etc.).

Core Workflow

1. Inventory & Context
   • Collect the binary, crash artifact (core, minidump, ASAN log, etc.), input that triggers it, environment details.
   • Run binary_context.py immediately for quick static metadata.