ldapenum - A new tool that enumerates information from domain controllers

From: James Brown (ldapenum_at_hotmail.com)
Date: 02/17/05

  • Next message: Kurt Seifried: "Re: Cryptocard database" 
    To: pen-test@securityfocus.com
Date: Thu, 17 Feb 2005 12:50:23 +0000

    ldapenum is a perl script designed to enumerate system and password
    information from domain controllers using the LDAP service when IPC$ is
    locked. The script has been tested on windows and linux.

    the script is capable of enumerating system and password information from
    domain controllers. It is also capable of launching clever password attacks
    that use the enumerated password information to prevent lockouts.

    The tool can be downloaded from: https://sourceforge.net/projects/ldapenum

    Enjoy!

    Roni Bachar & Sol Zehnwirth

    _________________________________________________________________
    Don’t just search. Find. Check out the new MSN Search!
    http://search.msn.click-url.com/go/onm00200636ave/direct/01/

  • Next message: Kurt Seifried: "Re: Cryptocard database"

    Relevant Pages

    • ldapenum - tool for enumerating information from domain controllers
      ... ldapenum is a perl script designed to enumerate system and password ... information from domain controllers using the LDAP service when IPC$ is ... The script has been tested on windows and linux. ...
      (Security-Basics)
    • Re: How to view current logged on users in active directory
      ... If that is all you want, who has constant connections to domain controllers, you can use the "net sessions" command on your domain controllers or if you want to do it remotely google for the netsess tool. ... Is a user who interactively logs into one ID and then uses runas to start an application as another ID logged on as that user? ... What if it is a /netonly use of runas and the auth doesn't occur until the user touches a remote resource and the use is only successfully that new user at the remote resource, ... If you are looking for who is interactively logged onto workstations, you can implement some sort of logon/logoff script mechanism with GPOs, but this will require 2K or better clients for all machines and it will only capture info for people who interactively log on or log off, for instance, if someone uses runas or net use /user it will not catch those, neither will it update users as logged off if the log off script doesn't run say the user hibernates or suspends or just shuts the PC off. ...
      (microsoft.public.windows.server.active_directory)
    • Re: delete computer
      ... Your script can check the operatingSystem attribute to make sure the ... the ability to delete domain controllers ... would belong only to domain admins; for member servers this might be ... I delegate control to manage workstations on the OU level and will omit ...
      (microsoft.public.scripting.vbscript)
    • Re: Change password
      ... You are trying to communicate with a workstation using LDAP://, ... and servers don't respond to LDAP, only domain controllers. ... You need to communicate directly with the PC using the WINNT:// ... I have tried this script ...
      (microsoft.public.windows.server.scripting)
    • Re: backup Event log & clear
      ... I would put the names of the 40 domain controllers into a list, ... then invoke the script for every name in that list. ... Basically I am plaaning to use this in group policy for domain controller ... So in single instant using group policy I am planning to take backup & ...
      (microsoft.public.scripting.vbscript)