ctf.nitaimaarek.com Learn Leaderboard Log in Sign up

Learn / Network / In the response / Catch a token in a redirect

Catch a token in a redirect

Practitioner 20 pts

Goal: Read the one-time token the server put in a 302 Location header.

Capture it yourself — real traffic

  1. Open Wireshark on your active interface and start a capture. Display filter for this level: http.response.code == 302. No GUI? sudo tcpdump -i any -w cap.pcap port 9080.
  2. Open the plaintext lab and click Generate traffic once.
  3. Stop the capture. The secret is in the Location header on the /old-report 302 response. Expand the 302's headers and read Location: /reports/view?token=… — take the token.

Open the plaintext lab (:9080) →

Genuinely unencrypted — the secret exists only on the wire, never on the page.

Hints

Open in order — they nudge, not solve.

Hint 1

The page hit /old-report, which 302-redirects. Find the response (filter http.response or http.response.code == 302).

Hint 2

Expand its headers for Location: — the browser followed it instantly, but the header is right here.

Hint 3

The token in that Location URL (REDIR-…) is the answer.

Log in or sign up to submit your answer and save progress.

← Roadmap Skip for now →