Mercer Bell runs professional exams online. An attempt has a window, and the window for this paper closed at 23:59 on 3 November.
Candidates sit these papers all over the world, so the window is expressed in local time: 23:59 wherever the candidate is. The client declares which that is, because offline mode lets a candidate work through a connection drop and submit when it comes back.
It is now 09:31 UTC on 4 November. Your attempt is finished and unsubmitted.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Submit this attempt after the window has closed.
“A deadline expressed in local time has to be evaluated in the local time the client reports.”
Compare instants, not local times. Store the deadline as an absolute moment per candidate, resolved from their registered centre or region when the attempt is issued, and compare it against the server's clock at submission. Keep the declared zone for display only. Add a test that submits after the window with a zone far to the west and expects a refusal.
Anywhere a rule is expressed in local time and the locale arrives in the request: submission deadlines, cut-off times for same-day dispatch, market open and close, promotional end dates, statement periods, out-of-hours surcharges, rate limits reset at midnight. The same shape appears with any client-declared frame: currency, locale, unit system, calendar. The check is to ask which value in the request the comparison depends on, and whether the client chose it.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.