JWT Misconfiguration
Inspect JSON Web Tokens and learn exactly where validation commonly fails.
Scenario
The sandbox issues JWTs and verifies them to authorise requests. Its verification has a realistic flaw — think algorithm handling or missing claim checks.
Objective
Identify the token-validation flaw in the sandbox and describe correct verification.
Your approach
- Decode and read the token's header and payload (they're not secret).
- Determine how the server verifies the token.
- Identify the specific validation weakness.
- Document the flaw and its impact on authentication/authorization.
- Describe correct verification: pinned algorithms, signature check, full claim validation.
Rules of engagement
Run this lab only in the isolated environment provided — the downloadable bundle runs on your own machine in a private Docker network. Only interact with the lab's target, keep testing non-destructive, and never use these techniques on systems you don't own or aren't authorised to test. When you've met the objective, submit the flag (format SS{...}) to score.
Remediation focus
Pin expected algorithms, verify signatures with the correct key, validate iss/aud/exp/nbf, keep lifetimes short, and use a vetted library.
Deliverable
Write up what you did, what you observed, the business impact, and a clear remediation — exactly as you would in a professional report.
Hints
Hint 1
Re-read the matching knowledge-base entry before you start.
Hint 2
Capture reproducible evidence as you go — you'll need it for the write-up.
Hint 3
For every finding, identify the single control that would prevent it.
Study the theory
Read the JWT Misconfiguration knowledge-base entry