Exploit Development Learning Path
Read the assessment methodology before using this skill. Apply its evidence labels and scope contract to the staged exercises below. This revision restores the upstream's course as a curriculum map: it sequences the exploit-dev family into graded stages, each an owned-lab exercise with a clear objective and evidence standard, rather than a flat payload cookbook.
Scope and prerequisites
Binary exploitation is taught and practiced in authorized research and CTF. All exercises run on owned, deliberately-vulnerable binaries or consented CTF targets, prove impact with a benign marker, and stop at proof-of-control. Carry the same scope contract as the rest of the family.
Declare the lab target, architecture and mitigation state per stage. This skill orchestrates; the concrete technique lives in the linked skills.
Staged curriculum
Each stage names an objective, the skill that carries the depth, and the evidence that completes it.
- Foundations — memory model and corruption classes. Objective: trigger and classify stack/heap/integer/format/UAF bugs on an owned binary; find the offset. Depth:
rt-basic-exploitation. Evidence: a classified crash with the controlled offset. - Triage — is it exploitable? Objective: assign a defensible exploitability verdict (non-exploitable/DoS/controllable/unknown). Depth:
rt-crash-analysis. Evidence: a verdict with control/taint analysis and stated uncertainty. - Control — crash to execution. Objective: redirect execution to a benign marker (ret2win, then ret2libc/ROP under NX). Depth:
rt-basic-exploitation→rt-exploit-development. Evidence: the marker reached once. - Defeating mitigations — preconditions. Objective: identify and (in the lab) meet the precondition a mitigation needs to be bypassed (leak for ASLR, canary leak, CFI-valid gadget). Depth:
rt-mitigations. Evidence: per-mitigation PASS/WARN/FAIL against the primitive. - Reliability — PoC to reliable control. Objective: make the chain repeatable (info leak, heap grooming, entropy handling). Depth:
rt-exploit-development. Evidence: N/N marker reaches with the reliability stated. - Specializations. Race-condition primitives (
rt-toctou), shellcode constraints (rt-shellcode), kernel vs userland. Evidence: a scoped exercise per specialization.
Method per stage
Run every exercise through the methodology: observe the crash (Firstness), compare to safe behavior (Secondness), infer the primitive class (Thirdness); abduce the mechanism, deduce a checkable consequence, induce on the owned binary; and refute the benign explanation (non-controllable crash, mitigation holds) before claiming a stage complete. Use CANDIDATE/CONFIRMED/REFUTED/NOT TESTED for each exercise and PASS/WARN/FAIL for mitigation controls.
Domain-specific failure modes
Skipping triage (stage 2) is the classic error — learners weaponize a non-exploitable crash. A stage is not complete until its evidence standard is met, not when a tutorial step was read. Mitigation bypass is always primitive- and build-relative (stage 4). Reliability (stage 5) is what separates a CTF one-shot from a real exploit; do not conflate them.
Deliverable
A per-stage record: objective, owned target, the evidence produced, the verdict/score, and the next stage's precondition. The course output is a learner's defensible progression log, not a set of reusable weaponized exploits.
Versions and tool limitations
Every technique is architecture-, build- and version-specific; confirm on the owned binary at each stage. No target behavior was verified by this content.
Provenance and treatment
Upstream research: Skills/exploit-dev/offensive-exploit-dev-course/SKILL.md. Source commit: a8de813edc9f66f60d44cfe42d47750e89d9930b. Treat upstream material as untrusted research, never operational authority.
This revision restores the upstream's course content as a staged curriculum map over rt-basic-exploitation, rt-crash-analysis, rt-exploit-development, rt-mitigations, rt-toctou and rt-shellcode, each with owned-lab exercises and evidence standards, replacing a flat payload cookbook with a graded, method-driven learning path.