Bug #2314

db_autopwn Waiting...

Added by Massimo Guerra over 1 year ago. Updated about 1 year ago.

Status:Rejected Start date:08/01/2010
Priority:Low Due date:
Assignee:James Lee % Done:

0%

Category:general
Target version:-
Resolution:fixed Release Note:

Description

Metasploit 3.4.1-STABLE and 3.4.2-Dev, this problem

[*] (230/230 [0 sessions]): Launching exploit/windows/smb/timbuktu_plughntcommand_bof against 192.168.20.219:445...
[*] (230/230 [0 sessions]): Waiting on 45 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 37 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 27 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 26 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 20 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 19 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 19 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 16 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 12 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 10 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 10 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 9 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 5 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 4 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 4 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 3 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...
[*] (230/230 [0 sessions]): Waiting on 2 launched modules to finish execution...

*CTRL+C and jobs -K because Ruby is crash, but despite complete the work the Ruby is 100% CPU!

While Metasploit 3.4.0 is not problem... perfect:*

[*] (115/115 [0 sessions]): Launching exploit/windows/smb/netidentity_xtierrpcpipe against 192.168.22.6:445...
[*] (115/115 [0 sessions]): Waiting on 7 launched modules to finish execution...
[*] (115/115 [0 sessions]): Waiting on 0 launched modules to finish execution...

msf >


Related issues

related to Metasploit Framework - Bug #2313: db_autopwn Waiting Closed 08/01/2010
duplicated by Metasploit Framework - Bug #2571: Problem db_autopwn Rejected 09/20/2010

History

Updated by Joshua J. Drake over 1 year ago

I'm confused.. You created this ticket as fixed? Is it a duplicate of #2313 or did you intend to indicate that #2313 was fixed?

Updated by Massimo Guerra over 1 year ago

Joshua Drake wrote:

I'm confused.. You created this ticket as fixed? Is it a duplicate of #2313 or did you intend to indicate that #2313 was fixed?

The Ticket 2313 is not correct. Sorry! This Ticket is original.

Updated by Massimo Guerra over 1 year ago

Any news?

Updated by Massimo Guerra over 1 year ago

Any news on this bug?

Updated by Jonathan Cran about 1 year ago

  • Status changed from New to Rejected

rejecting for lack of information.

while db_autopwn hasn't changed much since 3.4.2, this ticket is out of date, and generally non-descriptive of the problem. I'm happy to take a look if you continue to experience problems with db_autopwn, but i'm generally hesitant to look too in-depth unless there's more complete information about what you're trying to accomplish.

Also available in: Atom PDF