competition-cloud-metadata-path

Traces cloud metadata service reachability to credential issuance and accepted privilege in CTF sandboxes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? In cloud security CTF challenges, reaching an instance metadata endpoint is only half the battle; this Skill guides you through proving the full chain from metadata access to issued credentials to accepted cloud or cluster privilege, avoiding the common trap of demonstrating reachability without demonstrating impact. ## Core Features & Use Cases - Metadata Reachability Mapping: Records the exact path to metadata endpoints including headers, hop limits, session tokens, and whether access comes from local processes, pods, SSRF, or host routing. - Credential Issuance Proof: Documents how metadata responses become usable tokens, temporary credentials, or workload identities, capturing role names, audiences, issuers, and expiration. - Trust Path Reduction: Compresses findings into the smallest replayable chain from reaching surface to accepted privilege, pinpointing whether the weakness lives in reachability, role trust, or downstream policy. - Use Case: During a cloud CTF challenge, you obtain SSRF on a web pod. Use this Skill to systematically prove the SSRF reaches the link-local metadata endpoint, extract a workload identity token, and demonstrate which cloud API accepts it for privilege escalation. ## Quick Start Ask the orchestrator to route you here, then request: map the metadata reachability path from this pod and prove which credentials the metadata service issues and which cloud API accepts them.

Frequently Asked Questions about competition-cloud-metadata-path

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

FAQPage Schema
How do I prove cloud metadata service access leads to privilege escalation?

Map the reachability path to the metadata endpoint, extract the issued token or credential with its role and audience claims, then demonstrate a downstream cloud or cluster API accepting it. The skill reduces this to the smallest replayable chain as evidence.

What is the difference between instance metadata and workload identity in cloud CTF challenges?

Instance metadata is tied to the host or node identity, while workload identity is bound to a specific pod, task, or service account. The skill requires distinguishing which identity actually drove the privilege edge rather than mixing the two.

When should I use this skill instead of an SSRF exploitation skill?

Use this skill after SSRF reachability is already established and the challenge shifts to credential issuance and privilege acceptance. If you still need to prove the server-side fetch primitive itself, use the SSRF-to-metadata pivot skill first.

Why does proving metadata access alone fail in cloud security challenges?

Reaching a metadata endpoint does not prove a usable credential was issued or that any downstream API accepts it. Challenges typically require showing the full chain: reachability, token issuance, and an accepted privileged action.

What evidence should I collect for a metadata-to-privilege attack chain?

Keep the reachability side (route, headers, namespace, SSRF primitive), the identity side (role name, token claims, expiration, issuer, account binding), and the acceptance side (API action, resource access, or spawned workload effect) together in compact evidence blocks.