How To Own A Windows Domain

Description: <div style="text-align: justify;">Z (Z [at] wechall [dot] net) submitted this cool video to us. According to his submission:- I had to cut this video to a short one, so please use the pause button if something is too quick :) The mission is to create a new Windows domain administrator - in case we do not have any user in the domain or any local user at the workstation. <span style="font-style: italic;">Prerequisites: </span><br><br>1. Physical access to one of the domain member workstations for ~20 minutes. <br>2. Every local administrator user on the workstations have the same password. Strong or weak, it does not matter. NO social engineering, NO password stealer, NO password cracker, NO malicious code, NO exploiting zero-day or already patched vulnerabilities. <br><br>Tools used for the attack: <br><br>1. ophcrack (to get the local admin LM&NTLM hashes) <br>2. Offline NT Password & Registry Editor, Bootdisk / CD from Petter Nordahl-Hagen (to login as local admin) <br>3. pass-the-hash toolkit from Hernan Ochoa - Core Security (to authenticate with the hashes, so we do not have to crack them) <br>4. psexec from Mark Russinovich (to run remote commands) <br><br><span style="font-style: italic;">Demo architecture:</span> We have at least 3 computers: the workstation (WKS) for which we have physical access, the domain controller, and a workstation (ADMIN-WKS) with a logged in domain administrator (DomainAdmin). <br><br><span style="font-style: italic;">Steps: </span><br><br>1. Boot the workstation with ophcrack. Stop the cracking process, and save the hashes. View the hashes, and write the local administrator hashes down with pencil&paper (or copy it on a USB stick, etc.). <br>2. Boot in with the Offline NT Password & Registry Editor. Reset the local administrator password to blank, and reboot. 3. Login with administrator to the workstation with blank password. <br>4. Use iam.exe or iam-alt.exe to change the LM&NTLM hashes in the memory. <br>5. Copy the pass-the-hash toolkit to the admin-wks via an administrator share. <br>6. Run the whosthere.exe or whosthere-alt.exe to get the DomainAdmin LM&NTLM hashes. <br>7. Create a local user called DomainAdmin, and login into that profile. <br>8. Use iam.exe or iam-alt.exe with the DomainAdmin hashes to change the LM & NTLM hashes in the memory. <br>9. Right now we have the same privileges as the DomainAdmin, so we can create a domain admin for ourself. Or anything else we want in the domain (reset anyone elses password, read someone elses e-mail, etc.). <br><br><span style="font-style: italic;">Known limitations: </span><br><br>1. Some Windows versions / service packs are not compatible with the pass-the-hash toolkit, feel free to modify the source or debug the libraries to get the correct memory addresses. <br>2. Some AV engines detect pass-the-hash toolkit as malicious code, use AV evasion techniques against them. <br><br><span style="font-style: italic;">What is cool? </span><br><br>1. It does not matter how complex the local admin and domain admin passwords are. <br>2. It works even if the domain admins are forced to use smart cards for interactive login. <br>3. We have not used any of the attacks mentioned above, so it works on fully patched networks with security paranoid admins. <br></div><br><style type="text/css"> body { background: #FFF; } </style>

Tags: basics ,





Disclaimer: We are a infosec video aggregator and this video is linked from an external website. The original author may be different from the user re-posting/linking it here. Please do not assume the authors to be same without verifying.