CTF-Sandbox-Orchestrator/competition-jwt-claim-confusion/SKILL.md·查看原始 Markdown·索引

name: competition-jwt-claim-confusion description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for JWT, JWS, and JWE validation paths, header parsing, key selection, claim acceptance, audience and issuer checks, role derivation, and token-to-identity confusion bugs. Use when the user asks to inspect JWT headers or claims, key lookup, kid handling, alg confusion, audience or issuer validation, role claims, or explain how a token becomes accepted identity or privilege. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.


Competition JWT Claim Confusion

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 bug is not just "there is a JWT," but how headers, claims, and key selection turn into accepted identity.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Split the token path into parse, key lookup, signature or decryption, claim validation, and final acceptance.
  2. Record header fields, claims, key source, issuer, audience, and role mapping before mutating anything.
  3. Separate possession of a token from the exact service that accepts it.
  4. Keep parser behavior, trust policy, and resulting app session or privilege in one chain.
  5. Reproduce the smallest token-to-acceptance flow that proves the decisive confusion.

Workflow

1. Map Header And Key Selection

2. Prove Claim-To-Privilege Acceptance

3. Reduce To The Decisive JWT Path

Read This Reference

What To Preserve