Metrics with Names
A02 · ≈ 30 min · 0 solves
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
What counts as a valid solve
Public metrics labels disclose customer identifiers and an internal route.
GET /metrics.
prove that the deployed configuration exposes the protected synthetic value or privileged operation; the successful workflow returns the current rotating flag.
Work only inside your generated lab URL and submit the flag within 30 minutes.
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 · A02 · Metrics with Names
Objective
Public metrics labels disclose customer identifiers and an internal route.
Steps
- Start the isolated lab and inspect the root page for the intended diagnostic or configuration surface.
- Enumerate only the synthetic endpoint named by the scenario; no external target is required.
- Send: GET /metrics and inspect the labels
- Confirm the response exposes the misconfiguration and contains the rotating
flagfield (or embeds it in the returned synthetic artifact). - Submit the flag on the SecOne4all challenge page.
Expected proof
A successful response for metrics-sensitive-labels 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.