Interesting machine, learned a couple more useful tools. Thanks to those of you who posted hints, including @th3y , @VbScrub, @TazWake .
User is easy, but not always so easy to guess…really dumb and lazy, as they say.
Root is like @plackyhacker said, doesn’t require any modification to script, whatsoever. I had to place two files on the machine, an .exe and a .dll. It ran quickly and perfectly. The script started out as a Python version, and then someone turned it into another version.
Thanks @egre55 , for the machine. This was my fifth…
i have use enum4linux to brute username,but there is error,this is why?
[E] Server doesn’t allow session using username ‘’, password ‘’. Aborting remainder of tests.
i have use enum4linux to brute username,but there is error,this is why?
[E] Server doesn’t allow session using username ‘’, password ‘’. Aborting remainder of tests.
Try a different tool.
The problem with “enum” type scripts is that they run a lot of things and if you dont fully understand what they are doing, the output can be a bit confusing/overwhelming/misleading.
For example, I have zero idea why this response would happen, but it does imply it isn’t the best tool for this job.
I’m tearing my hair out with this easy to guess/lazy password. I’ve enumerated the list of user names but despite looping them through what feels like every obvious password I can think of, I’ve had no joy. Based on output from early enumeration, I been poking at S**. Is that where I’ve gone wrong?
I’m tearing my hair out with this easy to guess/lazy password. I’ve enumerated the list of user names but despite looping them through what feels like every obvious password I can think of, I’ve had no joy. Based on output from early enumeration, I been poking at S**. Is that where I’ve gone wrong?
You approach is correct. Take all the information you have right now - domains, obvious passwords, guesses, accounts, etc., and use that as the password list to try.
When you get it, you will realise you currently have the password.
I’ve tried so many users and passwords on this ■■■■■. Figures that the one account I got MSF to come up with the right ‘password’ was disabled. ■■■■ it all. I’ve been using all the four to six users that come up in the scans, all the ‘typical’ users you might see, and so many passwords variations, blanks, everything… Can it really be that obvious?
Annoyingly it really is that obvious when you find it.
All I can say is you might want to use CME rather than MSF and if you make a list of all the user accounts you can find and all the information you can find (domain names, profiles, usernames, timestamps, anything), you get it quite quickly.
The reality is if you’ve enumerated, you’ve seen the password.
I have enumerated all 10 users. I’m not seeing it. Please DM me some direction.
Hello everybody
can anyone hint me please with user, i found 2nd user creds and enumerate all in S****L directory but cant find way to get user.txt
cant undestand where i wrong
If you’ve connected as the second user, have you looked at their desktop?
i connect by s***t and cant find Desktop on u$ (
How did you connect? please DM me a cookie crumb. TY
■■■■, that root part got me fiddling with the code for hours. After reading enough articles, I realized that you don’t need to mess with the code. You just have to know how to execute the code and how it works!
Definitely expanded my knowledge with A**** and how vulnerable it is once the account has been compromised.
Hints:
USER - think how sysadmins create a new account in a lazy way. Now use that cred somewhere. Look for creds again. Use that creds somewhere.
ROOT - Once you found who you are. Google is your friend. There’s a lot of POC in the wild. Do a lot of research.
@c0met said:
ROOT - Once you found who you are. Google is your friend. There’s a lot of POC in the wild. Do a lot of research.
Yeah this is an issue now. Since this box went live there are now a lot more scripts and tools for this specific exploit (I even made one myself). So when people say “you don’t need to modify anything in the POC” its potentially misleading depending on which one you’re using.
FWIW the original POC on a fairly well known blog was po******* code and definitely did need one small part changing to work on this machine.
@VbScrub There is one that is ported to v******t that doesn’t require changes. But the changes came in the form of a parameter.
So yeah, YMMV on what poc you found.
Anybody willing to give me a nudge? Not the greatest with AD stuff…I’ve found and tested creds and can login to SL but there’s no Gs.xml like people are talking about…Where can I go next?
EDIT:
Managed to get user
No idea how to get root working…every ps1 attempt is riddled with errors like:
Missing closing ‘}’ in statement block or type definition.
The string is missing the terminator: '.
The splatting operator ‘@’ cannot be used to reference variables in an expression.
Anybody willing to give me some guidance on the root process? I have all the pieces, just can’t seem to get it to work
Edit:
Got root
Ditched PS1 scripts and used the uploading of 2 files method