Competition Kernel Container Escape
Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.
Use this skill when the decisive step is proving a boundary crossing between containerized context and host or higher-privilege kernel context.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Map runtime isolation first: namespaces, cgroups, seccomp, capabilities, LSM, and mount boundaries.
- Separate exploit prerequisite, primitive, and boundary-crossing proof.
- Record kernel version, config hints, runtime options, and reachable syscall surface.
- Keep instrumented observations separate from pristine challenge path.
- Reproduce one minimal primitive-to-boundary-crossing chain.
Workflow
1. Map Isolation And Kernel Surface
- Record namespace map, cgroup mode, capabilities, seccomp profile, AppArmor or SELinux state, mounted filesystems, and runtime sockets.
- Note kernel version, distro build hints, module exposure, and container runtime behavior.
- Keep host and container observations linked to exact node and context.
2. Prove Exploit Primitive And Crossover
- Show controllable input, trigger condition, affected object, and observable kernel or runtime state change.
- Capture before and after identity, namespace, mount, or process visibility to prove boundary crossing.
- Distinguish crash-only behavior from stable capability gain.
3. Reduce To Decisive Escape Chain
- Compress to: prerequisite state -> primitive trigger -> boundary crossing evidence -> resulting host-level capability.
- State whether root cause is kernel vulnerability, runtime misconfiguration, capability overgrant, or namespace leak.
- If path relies mostly on credential replay after initial foothold, hand off to Linux credential pivot skill.
Read This Reference
- Load
references/kernel-container-escape.md for isolation checklist, primitive checklist, and parity guidance.
What To Preserve
- Kernel and runtime context, capability set, seccomp or LSM state, and namespace map
- Primitive trigger data, boundary crossing evidence, and resulting capability
- One minimal reproducible chain from container context to host-relevant effect
1---2name: competition-kernel-container-escape3description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for kernel attack surface, namespace and cgroup boundaries, container isolation assumptions, syscall paths, and escape primitive verification. Use when the user asks to analyze container-to-host escape paths, kernel exploit prerequisites, namespace crossover, capability misuse, or prove whether an exploit primitive crosses the sandbox boundary. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.4---5
6# Competition Kernel Container Escape
7
8Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
9
10Use this skill when the decisive step is proving a boundary crossing between containerized context and host or higher-privilege kernel context.
11
12Reply in Simplified Chinese unless the user explicitly requests English.
13
14## Quick Start
15
161. Map runtime isolation first: namespaces, cgroups, seccomp, capabilities, LSM, and mount boundaries.
172. Separate exploit prerequisite, primitive, and boundary-crossing proof.
183. Record kernel version, config hints, runtime options, and reachable syscall surface.
194. Keep instrumented observations separate from pristine challenge path.
205. Reproduce one minimal primitive-to-boundary-crossing chain.
21
22## Workflow
23
24### 1. Map Isolation And Kernel Surface
25
26- Record namespace map, cgroup mode, capabilities, seccomp profile, AppArmor or SELinux state, mounted filesystems, and runtime sockets.
27- Note kernel version, distro build hints, module exposure, and container runtime behavior.
28- Keep host and container observations linked to exact node and context.
29
30### 2. Prove Exploit Primitive And Crossover
31
32- Show controllable input, trigger condition, affected object, and observable kernel or runtime state change.
33- Capture before and after identity, namespace, mount, or process visibility to prove boundary crossing.
34- Distinguish crash-only behavior from stable capability gain.
35
36### 3. Reduce To Decisive Escape Chain
37
38- Compress to: prerequisite state -> primitive trigger -> boundary crossing evidence -> resulting host-level capability.
39- State whether root cause is kernel vulnerability, runtime misconfiguration, capability overgrant, or namespace leak.
40- If path relies mostly on credential replay after initial foothold, hand off to Linux credential pivot skill.
41
42## Read This Reference
43
44- Load `references/kernel-container-escape.md` for isolation checklist, primitive checklist, and parity guidance.
45
46## What To Preserve
47
48- Kernel and runtime context, capability set, seccomp or LSM state, and namespace map
49- Primitive trigger data, boundary crossing evidence, and resulting capability
50- One minimal reproducible chain from container context to host-relevant effect
gabrielmoreira