> 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/useful-resources/exploit-development.md).

# Exploit-Entwicklung

Notizen zur Exploit-Entwicklung für Linux- und Windows-Buffer-Overflow-Labs, Offsets, Bad Characters, Shellcode und Payload-Auslieferung.

Übungsnotizen zu Buffer Overflows zum Erlernen der Grundlagen der Exploit-Entwicklung: Crash-Replikation, Offset-Ermittlung, Prüfung auf unerwünschte Zeichen, Platzierung von Shellcode und kontrollierte Ausführung der Nutzlast.

## Labs zur Exploit-Entwicklung

<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-folder-tree" style="color:$primary;">:folder-tree:</i></h3></td><td><h4>Linux-Buffer-Overflow - Benutzerdefiniert</h4></td><td>Benutzerdefinierte Linux-Buffer-Overflow-Notizen zum Erstellen von Exploits, Steuern des Ausführungsflusses, Entwickeln von Nutzlasten und Dokumentieren der Methodik der Speicherbeschädigung.</td><td><a href="/de/useful-resources/exploit-development/linux-buffer-overflow-custom.md">Linux-Buffer-Overflow - Custom</a></td></tr><tr><td><h3><i class="fa-file-code" style="color:$primary;">:file-code:</i></h3></td><td><h4>Linux-Buffer-Overflow - Agent-Binärdatei</h4></td><td>Notizen zu Buffer Overflows bei der Linux-Agent-Binärdatei für Crash-Analyse, Offset-Ermittlung, Nutzlasterstellung und Exploit-Validierung in CTF-ähnlichen Labs.</td><td><a href="/de/useful-resources/exploit-development/linux-buffer-overflow-agent-binary.md">Linux-Buffer-Overflow - Agent Binary</a></td></tr><tr><td><h3><i class="fa-envelope" style="color:$primary;">:envelope:</i></h3></td><td><h4>Windows-Buffer-Overflow - SLMail</h4></td><td>SLMail-Windows-Buffer-Overflow-Notizen für POP3-Fuzzing, Offset-Ermittlung, Auswahl von JMP ESP, Bereitstellung von Shellcode und Exploit-Validierung.</td><td><a href="/de/useful-resources/exploit-development/windows-buffer-overflow-slmail.md">Windows-Buffer-Overflow - SLMail</a></td></tr><tr><td><h3><i class="fa-folder-tree" style="color:$primary;">:folder-tree:</i></h3></td><td><h4>Windows-Buffer-Overflow - MiniShare</h4></td><td>MiniShare-Windows-Buffer-Overflow-Notizen für Fuzzing, EIP-Kontrolle, Bad-Character-Analyse, Shellcode-Generierung und Übung in der Exploit-Entwicklung.</td><td><a href="/de/useful-resources/exploit-development/windows-buffer-overflow-minishare.md">Windows-Buffer-Overflow - MiniShare</a></td></tr></tbody></table>

### Arbeitsablauf

1. Replizieren Sie den Crash und kontrollieren Sie die Eingabegröße.
2. Finden Sie den Offset, überprüfen Sie die Kontrolle über den Instruktionszeiger und identifizieren Sie Bad Characters.
3. Platzieren Sie Shellcode oder eine kontrollierte Nutzlast und dokumentieren Sie jeden Debugger-Prüfpunkt.
4. Halten Sie Exploit-Code, Screenshots, Offsets, Register und Befehle zur Nachvollziehbarkeit zusammen.


---

# 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/useful-resources/exploit-development.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.