c0nn3ct / armitage

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

Java runtime error in armitage when using escalation #166

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.right click on pwn pc 
2.go to meterpeter 3 - access then escalation
3.

What is the expected output? What do you see instead?

java runtime exception

What version of Metasploit are you using (type: svn info)? On which
operating system?
v4.9.3-2014061101 [core:4.9 api:1.0]

Which database are you using?

Please provide any additional information below.

Original issue reported on code.google.com by kevintyl...@gmail.com on 13 Jun 2014 at 12:45

Attachments:

GoogleCodeExporter commented 8 years ago
Go to the terminal where you started Armitage (or start it from a terminal). 
Paste in any messages you see there. Also, restart Armitage and try this again.

Metasploit's commercial module metadata pollutes the database in Kali Linux. 
That's the cause of this error. I take steps to detect this and fix it, but you 
have to restart for the fix to take effect.

Original comment by rsmu...@gmail.com on 13 Jun 2014 at 1:47

GoogleCodeExporter commented 8 years ago
paste in the error that i am getting into a terminal? i am not quite 
understanding what you mean. So should i do a msfupdate or just restart 
armitage?

Original comment by kevintyl...@gmail.com on 13 Jun 2014 at 2:03

GoogleCodeExporter commented 8 years ago
Hi,
Start Armitage from a terminal... just type armitage[enter] to do it. Debug 
messages will print to the terminal. To some this is a sign of a lazy 
programmer, and--they're right. I'm quite lazy. :()

When you do an msfupdate, this is when your database will get commercial module 
metadata. When you start Armitage, you'll see a message about this metadata in 
your terminal. Armitage will also print a message asking you to restart it for 
the fix to take effect.

If you do this, you should be OK. If you're not OK after a restart, that's 
something I want to look into.

Original comment by rsmu...@gmail.com on 13 Jun 2014 at 2:06

GoogleCodeExporter commented 8 years ago
okay standby. thank you very much! 

Original comment by kevintyl...@gmail.com on 13 Jun 2014 at 2:08

GoogleCodeExporter commented 8 years ago
armitage
[*] Starting msfrpcd for you.
[*] MSGRPC starting on 127.0.0.1:55553 (NO SSL):Msg...
[-] detected corrupt module cache... restart Metasploit for fix to take effect 
(#2)
[-] Metasploit Framework Exception: Invalid Module
[lib/msf/core/rpc/v10/rpc_base.rb:16:in `error', 
lib/msf/core/rpc/v10/rpc_session.rb:215:in `_find_module', 
lib/msf/core/rpc/v10/rpc_session.rb:203:in `block in rpc_compatible_modules', 
lib/msf/core/rpc/v10/rpc_session.rb:202:in `each', 
lib/msf/core/rpc/v10/rpc_session.rb:202:in `rpc_compatible_modules', 
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:365:in `dispatch_request', 
lib/rex/proto/http/server.rb:299:in `on_client_data', 
lib/rex/proto/http/server.rb:158: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: java.lang.RuntimeException: Invalid Module at armitage.sl:262
[-] detected corrupt module cache... restart Metasploit for fix to take effect 
(#3)
[*] Used the tab method: 192.168.6.129
[*] Remote Exploits Synced
[*] Starting Cortana on 192.168.6.129
[*] Creating a default reverse handler... 0.0.0.0:1875

Original comment by kevintyl...@gmail.com on 13 Jun 2014 at 2:13

GoogleCodeExporter commented 8 years ago
and i just restarted the metasploit service as well before i started armitage 
back up

Original comment by kevintyl...@gmail.com on 13 Jun 2014 at 2:14

GoogleCodeExporter commented 8 years ago
Roger. This is the message I'm looking for:

[-] detected corrupt module cache... restart Metasploit for fix to take effect 
(#2)
[-] Metasploit Framework Exception: Invalid Module
[lib/msf/core/rpc/v10/rpc_base.rb:16:in `error', 
lib/msf/core/rpc/v10/rpc_session.rb:215:in `_find_module', 
lib/msf/core/rpc/v10/rpc_session.rb:203:in `block in rpc_compatible_modules', 
lib/msf/core/rpc/v10/rpc_session.rb:202:in `each', 
lib/msf/core/rpc/v10/rpc_session.rb:202:in `rpc_compatible_modules', 
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:365:in `dispatch_request', 
lib/rex/proto/http/server.rb:299:in `on_client_data', 
lib/rex/proto/http/server.rb:158: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']

Restart Armitage and then try the escalate privileges menu option. It should be 
OK now. If it's not, type:

db_rebuild_cache in a console tab, wait one minute, and then restart it. If you 
have to take this particular step, let me know and I'll make my code do this on 
your behalf.

Original comment by rsmu...@gmail.com on 13 Jun 2014 at 2:20

GoogleCodeExporter commented 8 years ago
when i restarted it worked. but when i hit escalation nothing happened at 
all... bare with me i am new to this. is something supposed to pop up when i 
hit escalation?

Original comment by kevintyl...@gmail.com on 13 Jun 2014 at 2:22

GoogleCodeExporter commented 8 years ago
When you hit escalation, it will expand modules in the module tree that relate 
to escalating privileges on that particular host.

Original comment by rsmu...@gmail.com on 13 Jun 2014 at 2:25

GoogleCodeExporter commented 8 years ago
ohhh okay. i see that now. Can you recommend any sites that offer reading on 
exploiting/pentesting?

Original comment by kevintyl...@gmail.com on 13 Jun 2014 at 2:35

GoogleCodeExporter commented 8 years ago

Original comment by rsmu...@gmail.com on 13 Jun 2014 at 3:14