I sort of found the answer, by taking a look at the slides from defcon 17 about the browser_autopwn and its functionality and looking through the source of some of the modules. I'll post it in case anyone else is curious. For #1 the aurora exploit was superceded by ie_behaviors, which was superceded by ie_css_clip. For #2 You can control what exploits are used with the module by adding/modifying this information in the exploit:
include Msf::Exploit::Remote::BrowserAutopwn
autopwn_info({
:ua_name => HttpClients::IE,
:ua_minver => "6.0",
:ua_maxver => "8.0",
:javascript => true,
s_name => OperatingSystems::WINDOWS,
:vuln_test => nil, # no way to test without just trying it
})
The vuln_test is javascript that tests a condition for the exploit, a better example is from the mozilla_navigatorjava module
include Msf::Exploit::Remote::BrowserAutopwn
autopwn_info({
:ua_name => HttpClients::FF,
:javascript => true,
:rank => NormalRanking, # reliable memory corruption
:vuln_test => %Q|
is_vuln = false;
if (window.navigator.javaEnabled && window.navigator.javaEnabled()){
is_vuln = true;
}
|,
})
My guess is that there is no reliable way to test for java being enabled across multiple platforms, but then again I'm not very good with Javascript. Does anyone know of a good way to test for Java being enabled and better yet the installed version from JavaScript?


s_name => OperatingSystems::WINDOWS,