Of Challenge 2 - Index

Decode the .enc file using the key found in the Git history ( git reflog ):

Final Thoughts Challenge 2 teaches a critical real-world lesson: Directory indexing + exposed version control = Game over.

Happy hacking. Have a different approach to "index of challenge 2"? Drop your methodology in the comments below. index of challenge 2

Index of /challenge2 [PARENTDIR] Parent Directory [DIR] assets/ [TXT] readme.txt [?] flag.txt

Cracking the Code: A Deep Dive into the "Index of Challenge 2" Decode the

The flag is rarely the file named "flag.txt." Step 2: Analyzing the "Index" The phrase "index of challenge 2" is the clue itself. It suggests we need to think about how indices work—both in databases and in file structures.

Alex Mercenary | Category: Cybersecurity / CTF Walkthrough If you’ve been following along with our Capture The Flag (CTF) series, you know that Challenge 1 was a gentle handshake. Challenge 2 , however, is where the gloves come off. Drop your methodology in the comments below

Developers often forget that .git directories contain the entire history of a project, including deleted secrets. The "index" in Git isn't just a list of files—it's a staging area for your next commit. If an attacker can read it, they can travel back in time.

rm .git/index git reset HEAD . Suddenly, files that were "deleted" or hidden reappear. You’ll see a file named backup_ flag.txt (without the space) or user_flag.enc . After restoring the Git index, run ls -la . You’ll find a symlink or a hidden file like .secret/creds .

Let’s break down exactly how to solve it. When you navigate to the provided endpoint (let’s call it http://target/challenge2/ ), you are greeted with a raw Apache-style directory listing: