Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invoke-MimikatzWDigestDowngrade.ps1 is unable to lock a machine #29

Closed
samratashok opened this issue Dec 20, 2015 · 3 comments
Closed
Assignees

Comments

@samratashok
Copy link
Owner

A user, Peter, reported over email that Invoke-MimikatzWDigestDowngrade.ps1 is unable to lock a target machine. I was able to reproduce the bug. The user also suggested an improvement. I am currently testing it.

@samratashok samratashok self-assigned this Dec 20, 2015
@samratashok
Copy link
Owner Author

As suggested by Peter, tsdiscon.exe is able to lock the machine. Also, the machine unlock event which starts Invoke-Mimikatz in the script is not getting triggered in case of RDP connections. Testing different approaches. For example, tried Win32_ProcessStopTrace and Win32_ProcessStartTrace for TSTheme process, but no success, yet.

@samratashok
Copy link
Owner Author

Unable to figure out a WMI event that is triggered when a RDP session becomes active. Also, tsdiscon is not logging off a user, so WDigest downgrade doesn't work as well.

samratashok added a commit that referenced this issue Jan 1, 2016
@samratashok
Copy link
Owner Author

Turns out that the script worked fine for console logins (and is good for client side attacks as well). The support for RDP sessions has been added.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant