Lion Cipher Lab

Read LinPEAS output: find the Linux misconfigurations before an attacker does

Why it matters

An attacker who lands on a Linux box as a low-privilege user does exactly one thing next: they run an enumeration script like LinPEAS and read its output for a way up to root. As the defender, you win by reading that same output first — on a host you own — and closing every path before anyone else finds it. But the raw output is hundreds of lines of colour-highlighted findings, most of them harmless, and the skill that actually matters is triage: which highlighted line is a real road to root, which is background noise, and what is the concrete fix. This lab hands you a realistic LinPEAS…

What you'll learn

Steps in this lab

  1. The one rule, and what LinPEAS actually is
  2. How to read LinPEAS's colours — the severity legend
  3. The report — read the whole thing once before triaging
  4. Lead 1 — the SUID bit on /usr/bin/find (Red/Yellow)
  5. Lead 2 — the NOPASSWD sudo rule on python3 (Red/Yellow)
  6. Lead 3 — world-writable /etc/passwd (Red/Yellow)
  7. Lead 4 — the root cron job running a world-writable script (Red/Yellow)
  8. Lead 5 — the plaintext credential in a config and history file (Red)
  9. The judgment: a highlight is a lead, not a verdict — and how a pro prioritises
  10. What you actually learned

Open the full interactive lab →