> 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/writeups-ctf/vulnhub.md).

# VulnHub

ローカルの脆弱な仮想マシン向けVulnHubマシン攻略記事。Web列挙、サービス攻略、認証情報、権限昇格、root権限取得を扱う。

単独の脆弱な仮想マシンとローカルラボ演習のための VulnHub 攻略記事。

## VulnHub 手法

1. VMをインポートし、ターゲットIPを特定し、公開されているすべてのサービスを列挙する。
2. Webアプリ、サービス、認証情報、共有、およびローカル限定の管理画面をフィンガープリントする。
3. 最初に確実な足がかりを確保し、シェルアクセスを安定化する。
4. ローカルの設定ミス、弱い権限、カーネルの問題、または認証情報を利用して root または管理者権限へ昇格する。

## マシンのカテゴリ

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-linux" style="color:$primary;">:linux:</i></h3></td><td><h4>VulnHub Linux</h4></td><td>ローカルラボの列挙、Web攻撃、ファイルアップロード、phpMyAdminの悪用、認証情報のクラック、Linux権限昇格を扱う VulnHub Linux マシンの攻略記事。</td><td><a href="/ja/writeups-ctf/vulnhub/linux-vulnhub.md">VulnHub Linux</a></td></tr><tr><td><h3><i class="fa-windows" style="color:$primary;">:windows:</i></h3></td><td><h4>VulnHub Windows</h4></td><td>ローカルの脆弱な VM 演習、Windows サービスの列挙、攻撃、権限昇格に関する VulnHub Windows マシンのノート。</td><td><a href="/ja/writeups-ctf/vulnhub/windows-vulnhub.md">Windows VulnHub</a></td></tr></tbody></table>


---

# 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/writeups-ctf/vulnhub.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.
