Cron Troubleshooting Scenarios

advent2025 apache bash c caddy clickhouse cron csv data processing disk volumes dns docker envoy etcd git golang gunicorn hack haproxy harbor hashicorp vault helm java jenkins json kubernetes linux-other mongodb mysql nginx node.js php podman postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord systemd traefik

realistic / interviews new pro business

Cron

Cron job scenarios

#	Name	Level	Time	Type
1	Amsterdam: Cron Hijack	Medium	15 m	Hack New	Amsterdam: Cron Hijack Scenario: Amsterdam: Cron Hijack Level: Medium Type: Hack Access: Email Description: You are logged in as the user admin. A cron job (not a systemd timer) appears to be running as root every minute, related to a health check. We've discovered this set up may be insecure. Your mission is to find the running cron job, analyze it for a vulnerability, and exploit it to read the secret file at /root/secret.txt Save the secret string from the secret file to the file /home/admin/solution.txt. Test: `cat /home/admin/solution.txt` displays the same string that is in /root/secret.txt, with `md5sum /home/admin/solution.txt` returning `c6ef5d3ea5e937ae56f8635f91cc727a` (the solution string without an ending newline is also accepted) The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute. Time to Solve: 15 minutes.

Cron Troubleshooting Scenarios

Cron

Cron job scenarios

Amsterdam: Cron Hijack

Send Us Feedback or Get Notified