zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-kernel-container-escape
competition-kernel-container-escape
VerifiedInternal 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.9 KB |
| agents/openai.yaml | config | 379 B |
| references/kernel-container-escape.md | markdown | 987 B |
references/kernel-container-escape.md
View on GitHub# Kernel Container Escape Checklist
## First Pass
- Kernel version, runtime type, namespace map, cgroup mode, capability set
- Seccomp profile, AppArmor or SELinux mode, mounts, privileged sockets
- Potential primitives: syscall path, fs boundary, runtime API, namespace leak
## Chain To Reconstruct
1. Isolation baseline recorded
2. Exploit or misconfig primitive triggered
3. Boundary crossover evidence captured
4. Host-relevant capability appears
5. Chain reproduces from reset baseline
## Evidence To Keep Together
- Context side: kernel and runtime config, namespace and capability state
- Primitive side: controllable input, trigger, affected object, observables
- Effect side: identity change, host visibility, privileged action, persistence edge
## Common Pitfalls
- Treating container root as host compromise without crossover proof
- Mixing several primitives before proving one decisive chain
- Claiming escape from crash artifacts without stable capability evidence
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |