A04 · Cryptographic Failures · Insane

Constant-Time Missing

A04 · ≈ 60 min · 0 solves

500POINTS

MISSIONDiscover the weakness independently

Explore the application as a real target: map the exposed functionality, inspect requests and responses, build a working exploit, and recover the rotating flag. If you get stuck, the verified official solution is available below as an optional spoiler.

Rules of engagement

Stay inside the generated lab URL. Use only the synthetic accounts and data in this instance. The main SecOne4all site and external systems are out of scope.

Challenge brief

FLAG REQUIREMENTS

What counts as a valid solve

Goal

Use a controlled timing oracle to recover a signature one byte at a time.

Required interaction

POST /api/verifier/check.

Completion proof

recover a protected value or produce an accepted synthetic forgery through the application service; the successful workflow returns the current rotating flag.

Session rule

Work only inside your generated lab URL and submit the flag within 60 minutes.

VERIFIED WALKTHROUGH

Official solution

Contains the complete exploitation path. Open it only when you want the spoiler.

Reveal official solutionStep-by-step · verified against the live lab

Official solution · A04 · Constant-Time Missing

Objective

Use a controlled timing oracle to recover a signature one byte at a time.

Steps

Start the isolated CipherBank workspace and inspect its service operation and requests.
Capture the synthetic cryptographic artifact, token, oracle response, or protocol negotiation output.
Exploit the cryptographic design or implementation failure: POST candidate hex signatures to /api/verifier/check; use Server-Timing to select each of four bytes by the longest matched prefix, then submit the recovered tag.
Confirm the recovered secret, accepted forgery, or bypass returns the rotating instance flag.
Submit the exact flag before stopping or expiring the instance.

Expected proof

A successful response for mac-timing-oracle returns the instance-specific rotating flag. The flag is valid only for the current player and running instance.

Safety boundary

Use only the generated lab URL. No request to the main site, another user, or an external service is part of this solution.