Security lab
JWT Key ID Confusion
The JWT verification code selects a signing key from the kid header without validating that it belongs to the expected issuer or environment, opening a classic key-confusion vector.
Lab objective
Forge a JWT with a malicious key identifier and privileged payload so the backend accepts an unexpected signer and exposes the admin token.
Tools you will use
- browser
- Burp Suite
- curl
What this lab teaches
This lab is a self-contained exercise hosted in an isolated, per-user sandbox. You are given a clear objective, the tools typically used for the technique, and a guided set of hints. Because every sandbox is disposable and network-isolated, you can experiment freely, make mistakes, and reset the environment without affecting any real system.
Hints & approach
- 01The header contains a kid value used to select the verification key.
- 02If that key is attacker-controlled or mistakenly accepted, the application may trust the wrong signer.
- 03The backend should reject arbitrary key IDs, but this one does not.
How the sandbox works
When you start the lab, Vulnarex provisions an isolated, per-user environment and opens it in a new tab. Each session has its own target and state, so nothing you do here can affect another learner or any external system. You can reset the environment at any time and re-approach the challenge from a clean slate.