search

hpetr / armitage

Automatically exported from code.google.com/p/armitage
0 stars 0 forks source link

Metasploit Framework Exception: Invalid Module #162

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
When I lowered my exploit ranks to poor, this issue came up on my prompt;
[-] Metasploit Framework Exception: Invalid Module
[lib/msf/core/rpc/v10/rpc_base.rb:16:in `error', 
lib/msf/core/rpc/v10/rpc_module.rb:241:in `_find_module', 
lib/msf/core/rpc/v10/rpc_module.rb:109:in `rpc_options', 
lib/msf/core/rpc/v10/service.rb:152:in `block in process', 
lib/ruby/1.9.1/timeout.rb:68:in `timeout', 
lib/msf/core/rpc/v10/service.rb:152:in `process', 
lib/msf/core/rpc/v10/service.rb:90:in `on_request_uri', 
lib/msf/core/rpc/v10/service.rb:72:in `block in start', 
lib/rex/proto/http/handler/proc.rb:38:in `call', 
lib/rex/proto/http/handler/proc.rb:38:in `on_request', 
lib/rex/proto/http/server.rb:363:in `dispatch_request', 
lib/rex/proto/http/server.rb:297:in `on_client_data', 
lib/rex/proto/http/server.rb:157:in `block in start', 
lib/rex/io/stream_server.rb:48:in `call', lib/rex/io/stream_server.rb:48:in 
`on_client_data', lib/rex/io/stream_server.rb:192:in `block in 
monitor_clients', lib/rex/io/stream_server.rb:190:in `each', 
lib/rex/io/stream_server.rb:190:in `monitor_clients', 
lib/rex/io/stream_server.rb:73:in `block in start', 
lib/rex/thread_factory.rb:22:in `call', lib/rex/thread_factory.rb:22:in `block 
in spawn', lib/msf/core/thread_manager.rb:100:in `call', 
lib/msf/core/thread_manager.rb:100:in `block in spawn']
[*] Warning: expected iterator (@array or &closure)--received: $null at 
attacks.sl:128

Is this issue due to my framework or armitage?

Original issue reported on code.google.com by LispMonk...@gmail.com on 13 Feb 2014 at 7:01

GoogleCodeExporter commented 9 years ago 
I suspect framework. In the terminal where you started armitage, did you have a 
message along the lines of [-] database corrupt - please restart. If so, then 
this was a temporary thing. MSF comingles module metadata for their commercial 
and open source stuff in the same database table. This wreaks havoc for a tool 
like Armitage because when you try to touch their precious, it barfs with an 
error. I try to detect this and fix the database. When I see an error like 
this, that's what I usually think it's from. (so look for that restart message 
and heed it).

The message should only happen once per update (because after it's fixed, no 
reason to show it to you).

When I get a free moment, I'll try to reproduce this. I don't use Find 
Attacks/Hail Mary much. I change my exploit settings to Poor even rarer. If I 
can't reproduce this, I'm going to close the ticket.

Original comment by rsmu...@gmail.com on 14 Feb 2014 at 1:32