One Request Away No. 25 Streak 0 Solved 0 of 27

The deadline in your own time

Easy Business Logic 27 Oct 2026 Solved by 2

Scenario

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.

Request Tap any part of it
//// HTTP/1.1
Host:
Content-Type:
Cookie: mb_session=
answers=&tz=&offline=
No change — send it as it stands
Response

  • 01 What the server believed

    “A deadline expressed in local time has to be evaluated in the local time the client reports.”

  • 02 The fix

    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.

  • 03 Where else to look for this

    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.

The series

Every drill 27

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.

Do not stop here

A drill is one request.
A lab is the whole app.

Uphack labs are believable products with one realistic flaw buried in an ordinary feature. Same instinct, nothing highlighted — you get a running application and have to find it yourself.

Browse the labs
Registration is open Closes today

Turn the instinct into practice.

Drills are free and stay that way. The labs put the same reasoning against a whole application, and members get all of them. Registration is open until Saturday 19 September.

Create your account

Already a member? Sign in