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

metasploit exploit is failed, guy's help in this guest machine is vulnerable . #10923

Closed
11ash opened this issue Nov 5, 2018 · 3 comments
Closed

Comments

@11ash
Copy link

11ash commented Nov 5, 2018

[] Started reverse TCP handler on 192.168.43.119:4444
[
] 192.168.43.50:445 - Connecting to the server...
[] 192.168.43.50:445 - Authenticating to 192.168.43.50:445 as user 'pass'...
[-] 192.168.43.50:445 - Exploit failed: RubySMB::Error::UnexpectedStatusCode STATUS_USER_SESSION_DELETED
[
] Exploit completed, but no session was created.

Originally posted by @11ash in #10185 (comment)

@bwatters-r7
Copy link
Contributor

Hi there!
We'd like to help, but we need quite a bit more information.
What Exploit are you using?
What version of metasploit are you using?
What Operating system is metasploit running on?
What Operating system and service are you trying to exploit?
Please check the log files to see if there's more information.

@11ash
Copy link
Author

11ash commented Nov 7, 2018

Hello ,
i used exploit/windows/smb/psexec
versoin used is v4.17.22-dev
its running under parrot os and its version is release 4.3 64bit and kernel linux 4.18.0
am trying to exploit windows 7 ultimate 2009 - and windows xp R2 and trying to exploit smb services.
its also automatic
few days back while testing xp machine i was working i got meterpreter session but after update was happen . i started testing in windows 7 machine it shown me error.
again tried and tested with windows xp that also got the same error. both system are vulnerable .
even ms08_067_netapi also i used past week i tested in windows 7 and i not reaching.

@elogada
Copy link

elogada commented Nov 7, 2018

@11ash the update patched the problem, it turns out

@busterb busterb closed this as completed Nov 19, 2018
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

4 participants