> 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/ports-and-services/ftp-21.md).

# FTP - 21

匿名アクセス、ブルートフォース確認、ファイルアップロードの悪用、Webシェル、リバースシェルのためのFTP列挙ノート。

FTP は、匿名アクセス、書き込み可能なディレクトリ、バックアップファイル、または Web ルートへのアップロードが公開されている場合に、しばしば有用になります。まずはバージョン情報、匿名ログイン、書き込み権限、そしてアップロードされたファイルに Web サービスからアクセスできるかを確認してください。

## メモ

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>ブルートフォース</strong></td><td>Hydra と単語リストを使って FTP 認証情報を検証します。</td><td><a href="/ja/ports-and-services/ftp-21/ftp-brute-force-attack.md">FTP - ブルートフォース攻撃</a></td></tr><tr><td><strong>匿名アクセス</strong></td><td>匿名ログインと読み取り可能な FTP コンテンツを確認します。</td><td><a href="/ja/ports-and-services/ftp-21/ftp-anonymous-attack.md">FTP - 匿名アクセス</a></td></tr><tr><td><strong>シェルへのアップロード</strong></td><td>書き込み可能な FTP パスを悪用して、Web シェルやリバースシェルを配置します。</td><td><a href="/ja/ports-and-services/ftp-21/ftp-reverse-shell-webshell-attack.md">FTP - リバースシェルとWebシェル攻撃</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/ports-and-services/ftp-21.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.
