We must bear in mind that Windows File Explorer always tries to render the icon of any existing resource within a given location ( i.e. a directory )
Every resource has its own icon, whose location is specified within it
<SNIP>iconFile=<ICON_FILE_PATH><SNIP>
For instance, if we compromises a principal that has WRITE permissions over a certain SMB share, we could try to place a shortcut file within the latter whose iconFile points to a remote SMB server controlled by the attacker
So, when any user accesses the share location where the shortcut file has been placed using the Windows File Explorer, the latter will try to start an SMB session to the target in order to request this resource i.e. the shortcutβs iconFile
Then, it will be asked for authentication, so we will receive an incoming authentication that we can leverage to either relay it to another host or try to crack the Net-NTLMv2 response
Any shortcut file we create should start with the @ character to ensure that it appears on top of the share, and, hence, the file explorer parses it
Requirements
The controlled local/domain user account must have WRITE permissions over a location within an SMB share
Abuse
Verifying if the user account has write permissions over the share
An operator could craft a malicious file compatible with the Windows Media Player ( WMP ), which includes an UNC that points to the rogue server controlled by the attacker
Then, an SMB or HTTP server, depends on the client, is configured to listen for incoming connections, for which it requires authentication, so the client sends back the required authentication
Regarding the next step, the adversary needs to send the malicious file to the victim. For instance, letβs suppose that we face a web application that has an upload form, so we can upload the malicious file compatible with WMP that we have created previously
Once the victim receives and opens the given archive, the WMP will try to access the resource referenced in the specified UNC path
As stated, our server will ask for a valid authentication to the client, so we will receive an incoming authentication, which can be cracked or relayed
Requirements
The victim OS version must use WMP as the default media player for this type of files
The attacker must upload/write/send the malicious media file to an specific victimβs location
Abuse
Regarding NTLM Capture and the subsequent cracking, we can proceed as follows