Re: Trouble running smb-psexec.nse (NT_STATUS_INVALID_PARAMETER)

[Ron <ron () skullsecurity net>]

Hi David,

On Fri, 12 Feb 2010 13:39:00 -0700 David Fifield <david () bamsoftware com> wrote:
> If I modify smb.share_user_can_write to handle NT_STATUS_INVALID_PARAMETER
> the same way as NT_STATUS_ACCESS_DENIED, then the check gets past the
> Printer share and continues running. 
Hmm, I've never dealt with a printer share before. Good find! I suggest committing that. 

However it still fails later with
> NSE: smb-psexec: Entering cleanup() -- errors here can generally be ignored
> NSE: Stopping service: 1c59e4ba
> NSE: smb-psexec: [cleanup] Couldn't stop service: NT_STATUS_SERVICE_DOES_NOT_EXIST (svcctl.openservicew)
> NSE: Deleting service: 1c59e4ba
> NSE: smb-psexec: [cleanup] Couldn't delete service: NT_STATUS_SERVICE_DOES_NOT_EXIST (svcctl.openservicew)
> NSE: SMB: Couldn't delete ADMIN$\b3c98143.txt: NT_STATUS_OBJECT_NAME_NOT_FOUND
> NSE: SMB: Couldn't delete ADMIN$\b3c9b403.out: NT_STATUS_OBJECT_NAME_NOT_FOUND
> NSE: SMB: Couldn't delete ADMIN$\9b422d27.out.tmp: NT_STATUS_OBJECT_NAME_NOT_FOUND
> <snip>
> NSE: SMB: Couldn't delete print$\b3c9b403.out: NT_STATUS_OBJECT_NAME_NOT_FOUND
> NSE: SMB: Couldn't delete print$\9b422d27.out.tmp: NT_STATUS_OBJECT_NAME_NOT_FOUND
> NSE: smb-psexec: Leaving cleanup()
> NSE: Finished smb-psexec against 192.168.0.190.
> Completed NSE at 13:37, 1.27s elapsed
None of those are unexpected issues -- it tries to delete all kinds of files that may have been uploaded, just to be on 
the safe side. Nothing to worry about. 

> Host script results:
> | smb-psexec:
> |_  ERROR: Couldn't upload the service file: Couldn't find the file
I believe that error means that it couldn't find the file nmap_services.exe on your local filesystem. I thought I'd 
written a better error message than that, though, I'll have to check it out. 

> This is against Windows XP Professional SP3, with the login policy set
> to "Classic" (not "Guest only").
>
> David Fifield

Ron
-- 
Ron Bowes
http://www.skullsecurity.org
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/