-
Notifications
You must be signed in to change notification settings - Fork 14k
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
auxiliary/scanner/winrm/winrm_cmd: WinRM Authentication Issue (HTTP Error 500) #8900
Comments
What's the crypto scheme they use? A few are implemented in Rex and ruby-smb... Maybe we can port em if missing from winrm. |
The current WinRM implementation in Metasploit does not support encrypted communication or kerberos. |
this seems to be unchanged for 2 years now. I stumbled upon the very same problem during a Hackthebox machine (heist) again this year. Are there any plans to support this currently? A working implementation is provided (in ruby already) by https://github.com/WinRb/WinRM, which works kinda good. |
Same problem here with a different Hackthebox machine. |
Hi! This issue has been left open with no activity for a while now. We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. |
Hi! This issue has been left open with no activity for a while now. We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. |
I can still reproduce this error on Windows Server 2012 R2 (once remote management has been enabled with
Tested with |
Allowing unencrypted communications allowed
Although
|
I've just come across this as well. Setting Not a fix for the actual problem, but a possible workaround for anyone else wanting to use this. |
This was resolved by #15632, as encrypted comms was implemented with that. Replicating immediately before this PR (commit a1eef6a):
Fixed after the merge (commit ca6f957):
|
Steps to reproduce
Firing commands using the auxiliary/scanner/winrm/winrm_cmd fails with an HTTP 500.
Confirmed WinRM is working correctly using the following commands via meterpreter PowerShell extension:
(Yes, routing is setup properly). Victim host is Windows 10. Target is Windows Server 2012 R2. Both NTLM & Kerberos auth options confirmed open.
Wireshark on the victim is revealing interesting data.
Properly working request (from Invoke-Command):
Failing request (winrm_cmd):
Seems as though the second response of NTLM negotiation is being truncated by metasploit, but not positive.
System stuff
Metasploit version - 4.15.2-dev
I installed Metasploit with:
OS
What OS are you running Metasploit on? Kali
The text was updated successfully, but these errors were encountered: