22 July 2008 | 81,380 views

TSGrinder – Brute Force Terminal Services Server

Check For Vulnerabilities with Acunetix

This is a tool that has been around quite some time too, it’s still very useful though and it’s a very niche tool specifically for brute forcing Windows Terminal Server.

TSGrinder is the first production Terminal Server brute force tool, and is now in release 2. The main idea here is that the Administrator account, since it cannot be locked out for local logons, can be brute forced. And having an encrypted channel to the TS logon process sure helps to keep IDS from catching the attempts.

TSGringer is a “dictionary” based attack tool, but it does have some interesting features like “l337″ conversion, and supports multiple attack windows from a single dictionary file. It supports multiple password attempts in the same connection, and allows you to specify how many times to try a
username/password combination within a particular connection.

You can download TSGrinder 2.0.3 here:

tsgrinder-2.03.zip

Note that the tool requires the Microsoft Simulated Terminal Server Client tool, “roboclient,” which may be found here:

roboclient.zip

Or read more here.



Recent in Hacking Tools:
- masscan – The Fastest TCP Port Scanner
- drozer – The Leading Security Testing Framework For Android
- tinfoleak – Get Detailed Info About Any Twitter User

Related Posts:
- NiX Brute Force – Parallel Log-in Brute Forcing/Password Cracking Tool
- MS12-020 RDP Exploit Code In The Wild
- Patator – Multi Purpose Brute Forcing Tool

Most Read in Hacking Tools:
- Top 15 Security/Hacking Tools & Utilities - 1,869,572 views
- Brutus Password Cracker – Download brutus-aet2.zip AET2 - 1,059,999 views
- wwwhack 1.9 – Download wwwhack19.zip Web Hacking Tool - 624,859 views

Advertise on Darknet

17 Responses to “TSGrinder – Brute Force Terminal Services Server”

  1. Navin 22 July 2008 at 2:50 pm Permalink

    Hmm……l337 conversion seems all fancy but it don’t work with multiple threads open :(.

    But HOG does have some nice programs like URLScan DTS pack and TSEnum.

    Thanx for the link!!

  2. razta 22 July 2008 at 8:05 pm Permalink

    To protect against this kind of attack, you could disable the terminal server, or make sure you have a strong password policy in place. Pretty scary that the attack isent picked up by IDS because of the encryption, would the brute force logins be logged within windows some where?

  3. zupakomputer 22 July 2008 at 8:48 pm Permalink

    n0vv u-77 4rv3 t0 734rn 70 5p377 7h1n95 0u7 71k3 7h15 1n5t346:

    a=ay, b=bee, c=sea/see/cee, d=dee, etc

  4. Morgan Storey 31 July 2008 at 2:31 pm Permalink

    @ratza: Having used this before for the hell of it, and to show a client how bad having rdp open to the world is I can tell you that windows will not log it if it is the administrator account. If it is any other user it will. I think you can turn on verbose authentication logging as well.
    TSGrinder did get me into this clients server as well, it worked multi-threaded on my box, I think I had about 10 going at once, and it got the pretty simple password in about two hours, with nothing in the security log at all, and nothing on their firewall or IDS.
    This is why with windows you are better off disabling or renaming the admin account, and setting the admin accounts that you create to have account lockouts. Or simply don’t open rdp, or do both.
    I would like to see something like Denyhosts for RDP as then it would simply block the offending IP at the software level, slowing down majorly any brute force.

  5. splink 4 August 2008 at 9:05 pm Permalink

    While tsgrinder is a neat windows only RDP bruter, for linux users i would suggest the rdesktop brute force patch (http://www.foofus.net/jmk/tools/rdp-brute-force-r805.diff). Although i’ve never used TSgrinder it sounds ridiculously slow..

  6. Morgan Storey 5 August 2008 at 3:28 am Permalink

    @Splink: not having used the Rdesktop patch, I can say that from reading here: http://www.foofus.net/jmk/rdesktop.html that they sound very similar. There is a version of rdesktop for windows so maybe tsgrinder uses that as it seems quicker than the built in MSTSC.
    As I said I had 10 threads of tsgrinder going at once to a 2k3 box, it would take about 5-10 seconds per thread to check a password, that does make it pretty slow (about 1 password a second), but this is more the server slowing down authentications due to failures.
    You can work out that most admins are lazy, most passwords are non-complex, and most are 7 charecters or less, use a dictionary and you only have around a million words, that should only take 10-15 days. Thats pretty bad.
    Very good reasons to also have complex passwords, oh btw the one I found oh so long ago was in my dictionary it was very basic, no caps, no numbers, and a dictionary word, they have changed it so it is all good.

  7. MegaBlast 3 September 2008 at 1:23 pm Permalink

    Navin/Zupakomputer/Morgan,

    i have been trying to get this working and your posts suggest you have it working. I (and many others on forums) have an error when trying to run tsgrinder which is:

    “Couldn’t get handle to client window”

    I have looked at the dll versions, target machines etc and i am having no joy. Did you have to do anything to get this working and on what platforms?

    Thanks in advance!

  8. Navin 4 September 2008 at 3:40 pm Permalink

    Sure mate…we’re all here after all to help!! ;)
    Ya I did have a similar error quite a few times when I tried to run Tsgrinder from my home PC:

    “timed_Event_send_recv: Wait Failed: TIMEOUT
    Couldn’t get handle to client window”

    But it did work from the office PC

    I think the problem tht Ure facing is tht the server U’re trying to bruteforce has disabled remote access…..If its a high profile server then probably its unable to serve any more connection requests

    Try a diff server…I’d also suggest tht U read up on wht TSgrinder can do…. http://www.blackhat.com/presentations/bh-usa-03/bh-us-03-mullen.pdf

    Do report on how it works out,
    Cheers :)

    PS thnks fr the blog appreciation

  9. razta 23 October 2008 at 11:34 pm Permalink

    Im getting the same error in Vista, worked fine on XP.

  10. navin 24 October 2008 at 12:38 pm Permalink

    @ razta

    the same server tht U’d managed to connect to on XP din’t connect thru vista?? Or was it some diff. server??

    Read my last comment

  11. razta 26 October 2008 at 11:56 am Permalink

    @navin

    “the same server tht U

  12. tal 22 November 2008 at 9:20 pm Permalink

    hi
    im getting
    timed_Event_send_recv: Wait failed: TIMEOUT
    Couldn’t get handle to client window
    using xp

    did anyone got the solution ?

    please help//

  13. ethicalhack3r 25 November 2008 at 2:09 pm Permalink

    @tal
    Looks like it has timed out. Have you tried it on another box? Are you sure that the box your testing has a terminal server running?

  14. Soja 27 January 2009 at 4:34 pm Permalink

    timed_Event_send_recv: Wait failed: TIMEOUT
    Couldn

  15. CypherBit 30 January 2009 at 7:40 pm Permalink

    I too am getting:

    timed_Event_send_recv: Wait failed: TIMEOUT
    Couldn

  16. Jack Mehogoff 5 February 2009 at 6:01 am Permalink

    The newer Version of Windows Remote Desktop doesnt work with TSgrinder, the homos at MS made this possible, uninstall that garbage “update” and your problems will be solved, you cannot use TSgrinder on vista, because it comes with the homo client.

  17. Russ 19 March 2009 at 3:37 pm Permalink

    One thing you guys can all do to prevent this kind of attack is place a legal notice on your machines. This was originally intended to prevent brute force attacks on Terminal Servers. The program doesn’t know to click ok to continue… I have enabled this and tested with tsgrinder and was unable to get past it…

    A. You need to use the registry editor

    1. Start the registry editor (regedit)
    2. Move to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Winlogon
    3. Double Click the “LegalNoticeCaption”, and enter the text to be in the title bar, click OK
    4. Double Click the “LegalNoticeText”, and enter the warning text and click OK
    5. Close the registry and logoff, when you logon you will see the warning

    Works every time!