# CVE-2024-41570: Server-side request forgery in n/a

> Unauthenticated attackers can trigger SSRF in Havoc C2 server to send arbitrary network traffic from the team server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2024
- **Updated:** 9 Aug 2024
- **Also known as:** GHSA-5mcq-h782-4vg7

## What is CVE-2024-41570?

CVE-2024-41570 is a critical server-side request forgery vulnerability in n/a, published on 9 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Unauthenticated Server-Side Request Forgery (SSRF) in demon callback handling in Havoc 2 0.7 allows attackers to send arbitrary network traffic originating from the team server.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-41570?

It affects 1 product.


Products: Havocframework Havoc.

## How do I fix CVE-2024-41570?

No fix has been published for CVE-2024-41570 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41570 exists.

Public exploit code:

- CVE-2024-41570: Havoc C2 0.7 Teamserver SSRF exploit (github_poc): https://github.com/chebuya/Havoc-C2-SSRF-poc
- Havoc SSRF to RCE (github_poc): https://github.com/HimmeL-Byte/CVE-2024-41570-SSRF-RCE
- Automated Reverse Shell Exploit via WebSocket | Havoc-C2-SSRF with RCE (github_poc): https://github.com/diemoeve/CVE-2024-41570
- This is a modified version of the CVE-2024-41570 SSRF PoC from @chebuya chained with the auth RCE exploit from @hyperreality. This exploit executes code remotely to a target due to multiple vulnerabilities in Havoc C2 Framework. (https://github.com/HavocFramework/Havoc)  (github_poc): https://github.com/sebr-dev/Havoc-C2-SSRF-to-RCE
- This is a Chained RCE in the Havoc C2 framework using github.com/chebuya and github.com/IncludeSecurity pocs (github_poc): https://github.com/leo-mitch/CVE-2024-41570-Havoc-C2-RCE
- Expanded Exploit based on CVE-2024-41570 (github_poc): https://github.com/UnDefinedCS/HavocPwn

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41570 and fix it if it is affected.

What it is: CVE-2024-41570 is a critical server-side request forgery vulnerability in n/a, published on 9 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41570 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41570/ (Markdown: https://insights.sbomify.com/CVE-2024-41570/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41570
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41570
- OSV: https://osv.dev/vulnerability/CVE-2024-41570

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41570/
Summaries are generated and may contain mistakes; the official description above is the record.