zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-ssrf-metadata-pivot
competition-ssrf-metadata-pivot
VerifiedInternal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSRF reachability, internal route probing, metadata-service access, credential pivoting, and token-to-accepted-privilege chains. Use when the user asks to trace SSRF sources, internal hosts, metadata endpoints, link-local tokens, service-account credentials, or explain how a server-side fetch edge turns into accepted access. 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 | 372 B |
| references/ssrf-metadata-pivot.md | markdown | 1.0 KB |
references/ssrf-metadata-pivot.md
View on GitHub# SSRF Metadata Pivot Checklist
## First Pass
- SSRF source parameter, URL builder, method, headers, redirect handling
- Host allowlist or denylist logic, DNS behavior, scheme checks, proxy layers
- Reachable internal services, metadata endpoints, token responses
## Chain To Reconstruct
1. Server-side fetch primitive is confirmed
2. Internal or metadata endpoint is reachable
3. Credential or sensitive response is extracted
4. Downstream service accepts the recovered material
5. Resulting capability is reproduced
## Evidence To Keep Together
- Source side: endpoint, parameter, URL construction, normalization rules
- Pivot side: target host, metadata path, token fields, scope, expiry
- Acceptance side: target API or service, replay method, resulting privilege
## Common Pitfalls
- Treating metadata reachability as equivalent to privilege without acceptance proof
- Ignoring redirects, host normalization, or proxy-injected headers
- Skipping the final accepted-access step and reporting only response leakage
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: 472k | Updated | Claude CodeCodex | Unverified | 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 |