-
Notifications
You must be signed in to change notification settings - Fork 121
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
LDAP error bind 49 #1
Comments
hi! |
I have tried the latest version and the spn param with FQDN, the whole command like
I just review james forshaw's article found that maybe the problem is about
|
a valid apReq starts with "60", you cannot expect it to work with an invalid apReq :p |
I got same error however my apReq starts with Tested on Win10 1909 & Win10 20H2, the DC is Server 16. |
when I use FQDN, it printed like this: The command is And I'm sure the apReq starts with |
Same issue here. Anyone found a solution ? |
It looks like it has been patched. https://blog.0patch.com/2022/08/micropatching-krbrelay-local-privilege.html |
DC: WIN-1TCHOPTDEJ5 (Win2016 version [10.0.14393])
Computer in AD: PC-01 (Win10 version [10.0.17763.316])
Reproduce Steps:
test1
logged on PC-01KrbRelay.exe -spn ldap/WIN-1TCHOPTDEJ5 -clsid 90f18417-f0f1-484e-9d3c-59dceee5dbd8
, it will return following result and LDAP connection established.KrbRelay.exe -spn ldap/WIN-1TCHOPTDEJ5 -clsid 90f18417-f0f1-484e-9d3c-59dceee5dbd8 -console
to show a LDAP interactive prompt, it will return following result , any other attack argument will always return the bind error 49:Is there anything I missed?
The text was updated successfully, but these errors were encountered: