> 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.md). # Tomcat Notas de explotación de Apache Tomcat para acceso al manager, fuerza bruta de credenciales por defecto, despliegue de payload WAR, abuso del text manager y shells inversas. Notas de explotación de Apache Tomcat para acceso al gestor, credenciales débiles, despliegue de cargas WAR, puntos finales del gestor de texto, despliegue con curl y ejecución de shell inversa.

:server:

Gestor de texto

Abuso del despliegue del gestor de texto de Tomcat usando curl, cargas WAR y ejecución de shell inversa.Tomcat Text Manager

:server:

Despliegue de archivo WAR

Fuerza bruta de credenciales débiles del gestor de Tomcat, generación de cargas WAR, despliegue y notas sobre shell inversa.Archivo WAR de Tomcat
--- # 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.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.