I have completed many modules but sometimes you are really stuck. Most of the times I figure it out on my own or are helped with a little hint in this forum but on this one I’m really stuck. I tried it with sqlcmd on my own pc and a VPN but I really am lost in how to get to the linked server via the mssqlsvc account. Any help would indeed be appriciated…
Happy to help @cooljagdash . Could I ask for help on - Attacking Common Services | Attacking DNS ? I’ve used subbrute for domains and keep trying:
dig any
dig axfr
but nothing useful. Any hint would be greatly appreciated!
The flag is very simple. You are definitely on the right track. Perhaps you have misconfigurations or using the wrong parameters?
Make sure you are using inlanefreight.htb and not inlanefreight.com.
Make sure the resolvers.txt is using the target IP address.
Finally, make sure your dig command has the right parameters: dig [axfr|any|ns|mx|…] targetdomain @targetip
Heyo. I found the hash. Tried to crack it using hashcat; I tried the provided password list, as well as like 15+ different other playlist but I can’t crack it. Can anyone give a tip on which password list should be used?
Hi
i get the mssqlsvc hash and cracked it. but impossible to log with it ! i am completly stuck and in cant figure out what i have to do for get the perm for read the DBflag. please help me
Was about to post the same. Something isn’t quite right here .
I got the password for user mssqlsvc by acquiring the hash using responder and cracking it using hashcat.
Would have thought that with said password and username I’d be able to log in and enumerate the flagDB database to get the flag.
But neither mssqlclient.py, nor sqsh or sqlcmd (I installed the latter just to try this out) seem to accept the username & password as a valid pair. All 3 work with the htbdbuser credentials provided in the instructions.
Any tips on how to connect? I even tried using Remmina and RDP-ing into the server with the creds, but as nmap suggests, there’s no setup for that with this box.
Solved it yesterday - my tip would be to not mess around with the hash after you’ve cracked the password using hashcat or john. You only need the username and password for the second question.
And I didn’t use mssqlclient.py from impacket (though you could if you wanted to ).
For anyone having trouble cracking the hash. What I did is firstly use the whole Responder hash (starts with “MSSQLSVC::WIN-02 …”). Then I fed it into hashcat with cracking mode 5600 (for Responder hashes) and rockyou.txt worked for me while the provided password list didn’t.
If you then have trouble authenticating with mssqlsvc and its password, thnik about what authentication types MSSQL supports. Hint: mssqlclient.py doesn’t use the default authentication type.