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

# Desenvolvimento de Exploits

Notas de prática de buffer overflow para aprender os fundamentos do desenvolvimento de exploits: reprodução do crash, descoberta do offset, verificação de caracteres inválidos, posicionamento de shellcode e execução controlada da carga útil.

## Laboratórios de Desenvolvimento de Exploits

<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>Buffer Overflow no Linux - Personalizado</h4></td><td>Notas personalizadas de buffer overflow no Linux para construir exploits, controlar o fluxo de execução, criar cargas úteis e documentar a metodologia de corrupção de memória.</td><td><a href="/pages/424a6f10f16195d3bb06ac34876f5283b87a4a20">/pages/424a6f10f16195d3bb06ac34876f5283b87a4a20</a></td></tr><tr><td><h3><i class="fa-file-code" style="color:$primary;">:file-code:</i></h3></td><td><h4>Buffer Overflow no Linux - Binário do Agent</h4></td><td>Notas de buffer overflow do binário Agent no Linux para análise de crash, descoberta de offset, criação de payloads e validação do exploit em laboratórios no estilo CTF.</td><td><a href="/pages/43314c9765355572933e728c6552a0449ee7a13b">/pages/43314c9765355572933e728c6552a0449ee7a13b</a></td></tr><tr><td><h3><i class="fa-envelope" style="color:$primary;">:envelope:</i></h3></td><td><h4>Buffer Overflow no Windows - SLMail</h4></td><td>Notas de buffer overflow do SLMail no Windows para fuzzing de POP3, descoberta de offset, seleção de JMP ESP, entrega de shellcode e validação do exploit.</td><td><a href="/pages/a616219622fd6b0f68d28dab2b494340f6b9f513">/pages/a616219622fd6b0f68d28dab2b494340f6b9f513</a></td></tr><tr><td><h3><i class="fa-folder-tree" style="color:$primary;">:folder-tree:</i></h3></td><td><h4>Buffer Overflow no Windows - MiniShare</h4></td><td>Notas de buffer overflow do MiniShare no Windows para fuzzing, controle do EIP, análise de caracteres inválidos, geração de shellcode e prática de desenvolvimento de exploits.</td><td><a href="/pages/2cd39a8023d417b5b62c24803e5e6d1e6cde5b15">/pages/2cd39a8023d417b5b62c24803e5e6d1e6cde5b15</a></td></tr></tbody></table>

### Fluxo de Trabalho

1. Reproduza o crash e controle o tamanho da entrada.
2. Encontre o offset, verifique o controle do ponteiro de instrução e identifique caracteres inválidos.
3. Posicione o shellcode ou uma carga útil controlada e documente cada ponto de verificação do depurador.
4. Mantenha o código do exploit, capturas de tela, offsets, registradores e comandos juntos para garantir reprodutibilidade.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/pt-br/useful-resources/exploit-development.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
