> 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-easy/keeper-hackthebox-writeup.md). # Keeper HackTheBox Writeup Keeper HackTheBox Easy Linux machine writeup covering Abusing Request Tracker, Information Leakage, Obtaining KeePass password through memory dump (Privilege Escalation), with practical enumeration, e {% embed url="" %} {% hint style="warning" %} **Skills:** * Abusing Request Tracker * Information Leakage * Obtaining KeePass password through memory dump (Privilege Escalation) {% endhint %} ## Reconaisssance **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.

**Searching for open ports with Nmap: 22.80** ```bash nmap -p- --open -n -Pn -vvv --min-rate 5000 10.10.11.227 -oG allPorts ```

**Scanning the port version with Nmap:** Using Nmap to scan the port version and extracting the information into the "targeted" file: ```bash nmap -sCV -p22,80 10.10.11.227 -oN targeted ```

### Port 80 We discover the domain **keeper.htb** and a subdomain **tickets.keeper.htb**.

We add them to the `/etc/hosts` file:

## Request Tracker CMS Visiting **tickets.keeper.htb** we find an admin panel.

We test the default credentials of **Request Tracker**: ```plaintext Username: root Password: password ```

Connection successful!

In the **Admin → Users** section we find a user account: * User: * Password: Welcome2023!

#### SSH connection We use the credentials found to connect via SSH: ```bash ssh Inorgaard@keeper.htb ```

### Flag user.txt :)

## Privilege Escalation ### **KeePass database dump** We find a ZIP file `RT30000.zip` which we download to our machine: ```bash python3 -m http.server 8080 ``` ```bash wget http://10.10.11.227:8080/RT30000.zip ```

After extraction, we obtain: * **KeePassDumpFull.dmp** * **passcodes.kdbx**

We are trying to open `passcodes.kdbx` with KeePassXC: ```bash keepassxc passcodes.kdbx ``` It asks for a password. We try a bruteforce with **John The Ripper**, without success.

### **Keepass - memory dump analysis** {% embed url="" %} We exploit the `.dmp` file with a Python script: ```bash python3 poc.py KeePassDumpFull.dmp ``` This reveals unreadable characters. An online search leads us to a likely password:

**Result**: red porridge with cream

We use this password to unlock KeePass, giving us a **PuTTY encrypted key and root password**.

### Convert PuTTY key to OpenSSH format We need to convert the PuTTY key to OpenSSH format: ```bash puttygen key.ppk -O private-openssh -o id_rsa ``` Next, make sure your private key has the right permissions: ```bash chmod 600 id_rsa ``` #### **Connect to SSH server** ```bash ssh -i id_rsa root@10.10.11.227 ```

### 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-easy/keeper-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.