Ironhack — Cybersecurity Bootcamp · June 2026 · Pentesting / Blue Team

Ironhole: rebuilding the full chain of an attack, layer by layer

A CTF-style lab that covers the entire life cycle of a security compromise: from initial reconnaissance to privilege escalation to root.

The challenge

Ironhole is a controlled environment that simulates a complete security compromise. The target machine hides critical information behind several layers of obfuscation, steganography and vulnerable configurations — forcing you through the entire cycle of an ethical attack: reconnaissance, cryptography, brute force, exploitation and privilege escalation until root access is obtained.

The walkthrough, step by step
01

Access and reconnaissance

I configured local resolution of the simulated domain and ran a full port scan with nmap. Result: FTP (vsftpd), SSH (OpenSSH) and an Apache web server titled "Rabbithole".

02

Multi-layer decoding

The website hid a message behind four chained transformations: binary → decimal → Base64 → ROT13. Reconstructing the exact order with CyberChef revealed a key clue: enumerate subdomains.

03

Enumeration and targeted brute force

Virtual host enumeration uncovered a hidden subdomain with a custom password wordlist. A targeted brute-force attack against FTP (instead of a generic dictionary of millions of entries) found the credentials in seconds.

04

Steganography

The FTP contained an image with hidden data protected by a password (Steghide). Cracking the passphrase with Stegseek extracted a file with new credentials — this time for SSH access.

05

Access and privilege escalation

With an active SSH session, enumerating sudo permissions revealed two rules: one patched against a known CVE (CVE-2019-14287), and another configured too permissively, which allowed escalating straight to root without any exploit.

root@ironhole:~$ cat /root/flag.txt → THM{C0NGR4TUL4T10NS}
What I take away

The most demanding part was identifying the exact order of the four decoding layers — a single step out of order breaks the whole chain. From a security standpoint, the underlying lesson is clear: data obfuscation (Base64, ROT13) is not encryption or real protection, any analyst with basic tools can reverse it. The real vulnerability was not in the cryptography, but in an overly permissive permissions configuration — the most common human error, and the most dangerous.

4
Obfuscation layers reconstructed
2
Access vectors exploited (FTP + steganography)
Root
Final access level obtained
Scroll to Top