Description
Welcome to Failure Failure -- a high-available system. This challenge simulates a real-world failover scenario where one server is prioritized over the other. A load balancer stands between you and the truth -- and it won't hand over the flag until you force its hand.
Setup
Launch the challenge instance and note the host and port.
The service sits behind a load balancer that routes between a primary and failover server.
Solution
- Step 1SSH into the challenge serverUse the provided credentials to SSH into the challenge instance. The system runs a primary service and a secondary (fallback) service.ssh <user>@<HOST> -p <PORT_FROM_INSTANCE>
- Step 2Stop the primary serviceThe primary service is running and takes priority. Stop it with systemctl so the secondary service (which contains the flag) becomes active.sudo systemctl stop primary.service# Check that the secondary is now active:sudo systemctl status
- Step 3Read the flag from the secondary serviceWatch the journal output -- once the primary service is down, the secondary activates and prints the flag to the system journal.journalctl -f# Or check the service output directlysudo systemctl status secondary.service
Flag
picoCTF{f41lur3_f41lur3_...}
The flag lives in the secondary (failover) service. SSH in and stop the primary service with systemctl -- the secondary takes over and reveals the flag via journalctl.