competition-ssrf-metadata-pivot

Traces SSRF reachability into metadata credential extraction and accepted downstream access chains.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-ssrf-metadata-pivot-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-ssrf-metadata-pivot
Source: https://github.com/dbx0/skills/tree/main/skills/web-appsec/initial-access/competition-ssrf-metadata-pivot
Command: npx skills add https://github.com/dbx0/skills --skill competition-ssrf-metadata-pivot-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a CTF or sandbox challenge hinges on a server-side request forgery primitive, it is easy to stop at proving internal reachability and miss the decisive step: turning that reachability into extracted credentials that a downstream service actually accepts. This Skill structures the full SSRF-to-accepted-access chain so no critical evidence or pivot step is skipped. ## Core Features & Use Cases - SSRF Source Mapping: Records the fetch primitive, URL construction, normalization rules, redirect handling, and header behavior before any mutation. - Metadata Credential Pivoting: Traces metadata endpoints, token fields, role scope, and service-account credentials through to the service that accepts them. - Decisive Chain Reduction: Compresses findings into a minimal SSRF source to internal target to credential to accepted replay path, distinguishing read-only reachability from real privilege. - Use Case: During a cloud-themed CTF challenge, you find an image-fetcher parameter that fetches arbitrary URLs. Use this Skill to probe the link-local metadata endpoint, extract a service-account token, and prove the token is accepted by an internal API. ## Quick Start Ask the assistant to trace the SSRF source in the challenge, probe reachable metadata endpoints, and prove the extracted token is accepted by a downstream service.

Frequently Asked Questions about competition-ssrf-metadata-pivot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I exploit SSRF to access cloud metadata endpoints?

Identify the server-side fetch primitive such as a URL parameter, webhook, or image fetcher, then target the link-local metadata endpoint. Record token fields, scope, and expiry, and verify the credential is accepted by a downstream service before claiming privilege.

How to prove an SSRF vulnerability leads to real privilege escalation?

Reproduce the full chain: SSRF source, internal or metadata target, extracted credential, and accepted replay at a downstream API. Metadata reachability alone is not proof; the decisive evidence is a service accepting the recovered token.

What SSRF bypass techniques should I test first?

Test scheme filtering, host allowlist or denylist logic, DNS resolution behavior, redirect following, path rewrites, and proxy-injected headers. Record normalization steps before mutation so bypasses can be attributed to a specific parser or allowlist flaw.

When should I use this skill instead of a general cloud security skill?

Use it when the decisive path runs through server-side fetch capability and metadata-derived credentials in a CTF sandbox. If the task becomes mostly cloud identity policy analysis, hand off to a dedicated cloud metadata or IAM skill.

Why does my SSRF finding get rejected as low impact?

Reports are often rejected when they show only response leakage or internal reachability without accepted-access proof. Include the extracted credential scope and a minimal replay demonstrating the downstream service accepting the token.