View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003263Kali LinuxKali Package Bugpublic2016-05-01 23:362018-01-29 12:33
Reporterteward001 Assigned Tog0tmi1k  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionsuspended 
Product Version2016.1 
Summary0003263: Armitage does not work with version of Metasploit included on 2016.1 rolling
Description

This has been tested and confirmed, with an upstream reply noting that "Metasploit must have changed something" which in turn breaks how Armitage works.

In any case of using "check exploits" in Armitage on a target, it will fail with traceback similar to this:

msf > use unix/ssh/tectia_passwd_changereq
[-] Error while running command use: wrong number of arguments (given 1, expected 0)

Call stack:
/usr/share/metasploit-framework/modules/payloads/singles/cmd/mainframe/reverse_shell_jcl.rb:247:in to_s' /usr/share/metasploit-framework/modules/payloads/singles/cmd/mainframe/reverse_shell_jcl.rb:247:inreplace_var'
/usr/share/metasploit-framework/lib/msf/core/payload.rb:356:in block in substitute_vars' /usr/share/metasploit-framework/lib/msf/core/payload.rb:352:ineach_pair'
/usr/share/metasploit-framework/lib/msf/core/payload.rb:352:in substitute_vars' /usr/share/metasploit-framework/lib/msf/core/payload.rb:652:ininternal_generate'
/usr/share/metasploit-framework/lib/msf/core/payload.rb:312:in generate' /usr/share/metasploit-framework/lib/msf/core/payload/single.rb:40:ingenerate'
/usr/share/metasploit-framework/lib/msf/core/payload.rb:200:in size' /usr/share/metasploit-framework/lib/msf/core/payload_set.rb:91:inblock in recalculate'
/usr/share/metasploit-framework/lib/msf/core/payload_set.rb:78:in each_pair' /usr/share/metasploit-framework/lib/msf/core/payload_set.rb:78:inrecalculate'
/usr/share/metasploit-framework/lib/msf/core/module_set.rb:47:in create' /usr/share/metasploit-framework/lib/msf/core/module_manager.rb:91:inblock in create'
/usr/share/metasploit-framework/lib/msf/core/module_manager.rb:89:in each' /usr/share/metasploit-framework/lib/msf/core/module_manager.rb:89:increate'
/usr/share/metasploit-framework/lib/msf/ui/console/command_dispatcher/core.rb:2660:in cmd_use' /usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:427:inrun_command'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:389:in block in run_single' /usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:383:ineach'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:383:in run_single' /usr/share/metasploit-framework/lib/rex/ui/text/shell.rb:203:inrun'
/usr/share/metasploit-framework/lib/msf/ui/web/console.rb:71:in block in initialize' /usr/share/metasploit-framework/lib/msf/core/thread_manager.rb:100:inblock in spawn'

Steps To Reproduce

(1) Load Armitage.
(2) Run an nmap scan on a host to expose available services.
(3)"Find Attacks" as one would
(4) Attempt to use "check exploits" for any of the services, and you get traceback like shown before.

Additional Information

I have communicated with Armitage upstream with this reply:

It sounds like the Metasploit Framework changed in a way that is not compatible with one or more Armitage features. If you're concerned about this, I recommend that you use Armitage with the version of Metasploit it's blessed against (this is listed in the change log).

This suggests that, currently, they aren't going to fix it. Given that, this should be an issue left open until such time Armitage is fixed, or removed.

Activities

teward001

teward001

2016-05-01 23:39

reporter   ~0005172

The version of Metasploit Armitage is "blessed" against is two-years old, and very likely not to be included if we run a newer version here of MSF.
g0tmi1k

g0tmi1k

2018-01-29 12:33

administrator   ~0008161

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2016-05-01 23:36 teward001 New Issue
2016-05-01 23:39 teward001 Note Added: 0005172
2018-01-29 12:33 g0tmi1k Assigned To => g0tmi1k
2018-01-29 12:33 g0tmi1k Status new => closed
2018-01-29 12:33 g0tmi1k Resolution open => suspended
2018-01-29 12:33 g0tmi1k Note Added: 0008161