Skip to main content

pass the hash attack, detection and mitigation

Pass the hash (lateral movement)

pass the hash is a technique that enables an attacker using mimikatz tool to capture ntlm or lanman password hash of user from memory. successful attack allow the attacker to access directory or resources that the compromised user has authorize to access. 

how this attack works:

1. attacker first compromise a system or without taking consent of the user, attacker access that system and if that account has admin rights then leveraging that right attacker can use mimikatz to dump out all other ntlm password hashes from memory. or they can also compromise AD and take the ntds.dit file to capture hash from that file. 

2. using mimikatz tool they can embed the hash on the local token and starts moving through out the network laterally. it will not give attacker high level access on the target system. but if the compromised user account hash is authorized to high level access then attacker also will get the same. it depends based on the permission.


 you can see that steveholt is the user in this system and he is only has local admin rights as he belongs to local administrators group. he does not have domain admin rights. so he cannot access domain controller at any aspects. as he has local admin access so what we can do is launch mimikatz to dump out all the password hashes that is stored in memory in a search of if any domain admin ever access this system or not. if yes then we can find his hash and merged that with our token using mimikatz to elevate our privilege on our desired target system. 

after executing this command we found that there is an administrator in my domain who logged in my system for do some work someday. so copy his ntlm hash. 

after launching this command an elevated command prompt will appear. if you type whoami then it still tells you, you are steveholt but actually the command prompt has been appear by taking the token privilege of user Tony.Wonder.

now access the DC, you shall get access. 


 


Avi

 

 

Comments

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 ...

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   --...

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...