-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
rdp false positive #678
Comments
I have the same problem, how can I solve it? |
how can anyone expect to get help when giving no information? |
I encountered it and am curious. I got excited and thought I had creds for a pentest... redacted debugging output.
|
@ShyftXero and how do you know that the password is wrong? maybe the account is locked or the password expired. |
I was using freerdp to validate the finding. 0xC000006D STATUS_LOGON_FAILURE is what's returned when using what hydra reported. These are leaked creds we're using for a pentest. The password in question wouldn't adhere to the domain password policy so it's odd that it was accepted. ms docs explaining the error -> https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55 |
errors adjacent to the large blob of false-positives
|
@ShyftXero thank you, that is actually something I can work with :) |
Unfortunately, that machine was taken offline to mitigate some other findings during the pentest so I can't fully reproduce / validate that the creds aren't working. I'm sure it's meaningless because there's no actual exchange of auth material at this point but I went ahead and did as you asked in case it was still up... fresh git clone and -dvv
Like I said, the machine is INOP so impossible to reproduce... Sorry for the hassle. |
I will say I was trying to use creds that contained the windows domain prepended to the username
it could look like I was trying to escape the j ( |
I did try it at a later time with the |
how is correct ? |
idk man. computers. the |
anyway with |
i have the same issue. was trying to brute rdp with hydra in my home lab. it gave me false positive: the password for admin account was password1234 and it gives something else; hence false positive. tried another tool (crowbar) it gives the same false positive as well. might be related to rdp idk. `hydra -t 1 -dvv -f -l administrator -P /opt/rockyou.txt rdp://192.168.44.124 -s 3389 [DEBUG] Output color flag is 1 |
as i stated earlier; i checked the hydra_rdp.c file and it states it works on win 7, 10. so this could be the issue here for MY CASE. my lab machine is windows xp. checked the crowbar source code it also initiates the xfreerdp +auth-only option where hydra also uses freerdp library and also checks
when i try to login with terminal using xfreerdp to my xp machine with the given parameters ( +auth-only and /cert:ignore) it gives the same result with a false password. both debug output is exactly same. will try on win7 later. xp is already lost its vendor support. imo using ncrack with slow mode will solve our problems here. |
follow up in #923 |
1 of 1 target successfully completed, 1 valid password found
Hydra (https://github.com/vanhauser-thc/thc-hydra) finished at 2021-08-15 15:56:13
password dont match.
The text was updated successfully, but these errors were encountered: