Lubricy / armitage

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

auxiliary not accepting a module that only accepts one host and not an array (RHOST). #117

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  Calling the auxiliary module with a single IP address such as @1.1.1.1
2.
3.

What is the expected output? What do you see instead?
The trace (tron) does not show any errors; however, a wireshark capture shows 
that no traffic is ever leaves the building. 

What version of Metasploit are you using (type: svn info)? On which
operating system?
svn r15903 on in Backtrack 5 r2

Which database are you using?

Please provide any additional information below.

Original issue reported on code.google.com by m...@sph3r3.com on 28 Sep 2012 at 4:04

GoogleCodeExporter commented 9 years ago
Please provide an example that reproduces your issue and the exact output you'd 
like to see. On second read, I suspect that you're reporting a Cortana issue. I 
didn't get that at first.

Original comment by rsmu...@gmail.com on 28 Sep 2012 at 5:47

GoogleCodeExporter commented 9 years ago
You are correct on cortana ... my apologies for a very poor question.  I am 
using a metasploit module I have developed - which at this time only accepts 
one IP address for the RHOST input.  This said - I am trying to use the 
following cortana script.

on heartbeat_5m {
    println("[*] Faulting controller located at 172.16.1.30");
    auxiliary("cybati/micrologix_fault", @172.16.1.30);
}

Originally I was just using the on service_add function and the same logic in 
your documentation - then I switched away from that in trying to figure out 
where this simple script is failing.  

Original comment by m...@sph3r3.com on 28 Sep 2012 at 6:05

GoogleCodeExporter commented 9 years ago
Use @(172.16.1.30). That's a single element array for a single host. Auxiliary 
modules by convention accept RHOSTS and not RHOST. So if your module only takes 
RHOST, you may want to update it to take RHOSTS instead.

If all else fails, look at the module function to actually call the module 
manually and specify all of the parameters. You can do launch("auxiliary", 
"whatever/module", %(RHOST => "your option", SOMEVALUE => "something else"));

Launch won't transform what you've posted. Auxiliary makes assumptions about 
the module based on Metasploit's conventions.

Original comment by rsmu...@gmail.com on 28 Sep 2012 at 6:10

GoogleCodeExporter commented 9 years ago
Well .. that did it.  Due to my poor module implementation and not following 
the RHOSTS convention the auxiliary function would not work.  What I did find 
odd is that I could not capture any debugging from cortana or metasploit that 
represented a failure.  I turned on debug=true in the metasploit module too.  

So, the answer was to use the launch() function and directly call the 
parameters.  Thanks for your amazing late night response time and for the 
awesome tools.  Armitage, and now coupled with Cortana is absolutely awesome!

Original comment by m...@sph3r3.com on 28 Sep 2012 at 2:14

GoogleCodeExporter commented 9 years ago

Original comment by rsmu...@gmail.com on 5 Feb 2013 at 8:52