← Back to arena
A07 · Authentication Failures · Medium

Password Change Without Proof

A07 · ≈ 30 min · 0 solves

200POINTS
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

An unattended authenticated session can change the password without fresh credentials.

Required interaction

POST /password/change.

Completion proof

reach the protected synthetic account state without completing the intended authentication boundary; the successful workflow returns the current rotating flag.

Session rule

Work only inside your generated lab URL and submit the flag within 30 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 · A07 · Password Change Without Proof

Objective

An unattended authenticated session can change the password without fresh credentials.

Steps

  1. Start the isolated lab and inspect the advertised authentication or recovery entry point.
  2. Complete the normal first step to obtain the synthetic session, token, or account state.
  3. Exploit the authentication failure: POST /password/change with only new_password=new, omitting current_password.
  4. Confirm the bypassed identity boundary returns the rotating instance flag.
  5. Submit the exact flag before stopping the lab.

Expected proof

A successful response for password-change-no-reauth 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.