1---2name: exploit-development3description: Authorized exploit development and vulnerability research skill for lab environments, CTFs, owned software, crash analysis, memory corruption, exploitability assessment, fuzzing results, proof-of-concept design, and remediation. Use for defensive validation and education; avoid real-world weaponization, stealth, persistence, evasion, or unauthorized targets.4metadata:5 source: https://skillmd.com/skills/masriyan/exploit-development6---78# Exploit Development910## Authorization Boundary1112- Work only on owned code, lab targets, CTFs, or explicitly authorized research.13- Keep proof of concept minimal: demonstrate the bug and impact without persistence, evasion, automated exploitation at scale, or post-exploitation.14- Prefer root-cause analysis, exploitability classification, mitigations, and regression tests.1516## Workflow17181. Establish target version, build flags, architecture, mitigations, input vector, and crash artifact.192. Reproduce deterministically in an isolated lab with symbols and sanitizer output when possible.203. Triage root cause: bounds, lifetime, type confusion, race, injection, logic flaw, or unsafe parser behavior.214. Assess exploitability at a high level: control of instruction pointer, write primitive, info leak, sandbox, and mitigations.225. Provide a safe PoC or pseudocode only as needed to validate impact, then produce patch guidance and tests.2324## Defensive Outputs2526- Crash summary with environment and reproduction constraints.27- Root-cause explanation tied to source or disassembly.28- Severity rationale and affected versions.29- Patch strategy, hardening recommendations, and regression/fuzz tests.30