Skip to main content
CVE-2024-41570VulnerabilityPublished

CVE-2024-41570: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.9% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Immediately restrict outbound network traffic from the Havoc team server to only trusted destinations using firewall rules or network segmentation to limit SSRF exploitation scope. 2. Monitor network logs and server activity for unusual or unexpected outbound requests originating from the Havoc server, which may indicate exploitation attempts. 3. If possible, isolate the Havoc team server in a controlled environment with limited network access to reduce attack surface. 4. Engage with Havoc developers or the community to obtain patches or updates addressing this vulnerability as soon as they become available. 5. Implement strict input validation and sanitization on any user-controllable parameters related to demon callback handling to prevent injection of malicious URLs or payloads. 6. Conduct thorough security assessments of Havoc deployments to identify and remediate any exposure of the team server to untrusted networks. 7. Consider temporary suspension of Havoc usage in production environments until a fix is confirmed to mitigate risk. 8. Educate red team and security staff about the vulnerability to ensure awareness and prompt incident response if suspicious activity is detected.

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.

References

Community reviews

Loading reviews…