Lion Cipher Lab

Review captured HTTP in Burp: exposed tokens, weak headers, and risky parameters

Why it matters

Anyone can turn Burp Suite on and watch requests scroll past its HTTP history. The skill that actually pays is knowing what to LOOK for in that traffic — and web bugs live in the exact bytes of the request/response pair, not in a scanner's summary. This drill puts a realistic capture in front of you and teaches you to read it the way an assessor does: a session token sitting in a URL (already leaked to logs, caches and the Referer header), a login response whose cookie has no HttpOnly or Secure flag and whose headers set no CSP, a password sent in a GET, an error page that hands an attacker…

What you'll learn

Steps in this lab

  1. What this drill is — and why the request/response pair is where bugs live
  2. How to read a raw HTTP request and response
  3. The capture — your Burp HTTP history (read all five pairs first)
  4. Finding 1: a secret in the URL — treat it as already leaked
  5. Finding 2: audit the response headers — the cookie flags and the missing CSP/HSTS
  6. Finding 3: credentials in a GET that should have been a POST
  7. Finding 4: the error page is an information leak
  8. Finding 5: the SHAPE of an access-control bug — a predictable id
  9. When passive review is enough — and when you must actively test
  10. Do it better — the review habits that separate signal from noise

Open the full interactive lab →