# Overpass2 ## Overpass 2 - Writeup Overpass has been hacked! The SOC team (Paradox, congratulations on the promotion) noticed suspicious activity on a late night shift while looking at shibes, and managed to capture packets as the attack happened. Can you work out how the attacker got in, and hack your way back into Overpass' production server? **Date**: 16/03/2022 **Difficulty**: Medium **CTF**: *** ## Forensics - Analyse the PCAP ### What was the URL of the page they used to upload a reverse shell? First of all I downloaded the file available with this room and open it using Wireshark.

After reading a few registers, it seems like the url used to upload the reverse shell was this one:

### What payload did the attacker use to gain access? Let’s analyze the POST petition:

After taking a look to the registers, this one seems suspicious:

We can see that the system is asking for a password. Two registers after, we can see the entered password in clear text:

### How did the attacker establish persistence? It looks like the hacker has cloned a GitHub repository called ‘’backdoor’:

### Using the fasttrack wordlist, how many of the system passwords were crackable? The hacker performed a cat /etc/passwd and cat /etc/shadow revealing the following information: ```jsx root:*:18295:0:99999:7::: daemon:*:18295:0:99999:7::: bin:*:18295:0:99999:7::: sys:*:18295:0:99999:7::: sync:*:18295:0:99999:7::: games:*:18295:0:99999:7::: man:*:18295:0:99999:7::: lp:*:18295:0:99999:7::: mail:*:18295:0:99999:7::: news:*:18295:0:99999:7::: uucp:*:18295:0:99999:7::: proxy:*:18295:0:99999:7::: www-data:*:18295:0:99999:7::: backup:*:18295:0:99999:7::: list:*:18295:0:99999:7::: irc:*:18295:0:99999:7::: gnats:*:18295:0:99999:7::: nobody:*:18295:0:99999:7::: systemd-network:*:18295:0:99999:7::: systemd-resolve:*:18295:0:99999:7::: syslog:*:18295:0:99999:7::: messagebus:*:18295:0:99999:7::: _apt:*:18295:0:99999:7::: lxd:*:18295:0:99999:7::: uuidd:*:18295:0:99999:7::: dnsmasq:*:18295:0:99999:7::: landscape:*:18295:0:99999:7::: pollinate:*:18295:0:99999:7::: sshd:*:18464:0:99999:7::: james:$6$7GS5e.yv$HqIH5MthpGWpczr3MnwDHlED8gbVSHt7ma8yxzBM8LuBReDV5e1Pu/VuRskugt1Ckul/SKGX.5PyMpzAYo3Cg/:18464:0:99999:7::: paradox:$6$oRXQu43X$WaAj3Z/4sEPV1mJdHsyJkIZm1rjjnNxrY5c8GElJIjG7u36xSgMGwKA2woDIFudtyqY37YCyukiHJPhi4IU7H0:18464:0:99999:7::: szymex:$6$B.EnuXiO$f/u00HosZIO3UQCEJplazoQtH8WJjSX/ooBjwmYfEOTcqCAlMjeFIgYWqR5Aj2vsfRyf6x1wXxKitcPUjcXlX/:18464:0:99999:7::: bee:$6$.SqHrp6z$B4rWPi0Hkj0gbQMFujz1KHVs9VrSFu7AU9CxWrZV7GzH05tYPL1xRzUJlFHbyp0K9TAeY1M6niFseB9VLBWSo0:18464:0:99999:7::: muirland:$6$SWybS8o2$9diveQinxy8PJQnGQQWbTNKeb2AiSp.i8KznuAjYbqI3q04Rf5hjHPer3weiC.2MrOj2o1Sw/fd2cu0kC6dUP.:18464:0:99999:7::: ``` Let’s copy the shadow file information into a file in our system and crack it using John the Ripper and the fasttrack wordlist:

## Research - Analyse the code Now that you've found the code for the backdoor, it's time to analyse it. ### What's the default hash for the backdoor? First of all, let’s go to the backdoor repository to analyse the code:

Inside the code of the main.go file a hash can be found:

### What's the hardcoded salt for the backdoor? In the same files, this can be found:

Where verifyPass is:

So it belongs to a hardcoded salt. ### What was the hash that the attacker used? - go back to the PCAP for this! In the top lines of the main.go code, we can se that:

The flag -a is used to customize the hash: Now, back to Wireshark, let’s see how the hacker ran the backdoor:

### Crack the hash using rockyou and a cracking tool of your choice. What's the password? As we have seen before in the code, the hash format is sha512. I’ll try to crack it using John the Ripper, but I don’t remember how to crack salted hashes, so I’ll do a quick research: I create a file named hash.txt which will contain `hash$salt`:

Now I use John with the correct formar to crack the hash:

## Attack - Get back in! Now that the incident is investigated, Paradox needs someone to take control of the Overpass production server again. There's flags on the box that Overpass can't afford to lose by formatting the server! ### The attacker defaced the website. What message did they leave as a heading? Let’s visit the web page:

### Using the information you've found previously, hack your way back in! I suppose that the username is james, as the hacker has created his own RSA key for this user before:

I have no clues about how I can get that key to connect as the hacker... In the last line it seems as the hacker has opened a ssh service in port 2222.

I confirmed it using nmap. Maybe the user is CooctusClan and the password may be the one used to generate the salted hash? It worth a try:

Lol, it is hahaha ### What's the user flag? After a quick directory listing in the current and the james directories I found it.

### What's the root flag? As we probably will need root privileges to find that flag, let’s see if we perform privesc: Can run any command with sudo?

Ok, I forgot that I didn’t know james password... But I have cracked some users password no time ago:

Maybe the hacker has changed the passwords... Time to look to the crontab:

Nothing to do here. There are files with the SUID bit activated?

Last one is suspicious, it looks like a copy of bash but with SUID.

And... It is! Remainder: the option `-p` holds the file owner privileges when running the binary.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://angellm.gitbook.io/hacknotes/thm/2022/overpasstwo.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.