CVE-2024-39130: DumpTS · n/a
Affects DumpTSSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubwangf1978/DumpTSpkg:github/wangf1978/DumpTSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately restrict network access to DumpTS services by implementing firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Monitor DumpTS application logs and system stability closely for signs of crashes or abnormal behavior indicative of exploitation attempts. 3. Employ process supervision tools to automatically restart DumpTS services if they crash, minimizing downtime. 4. Engage with the DumpTS development community or vendor to obtain patches or updates addressing this vulnerability as soon as they become available. 5. Consider deploying intrusion detection systems (IDS) or anomaly detection solutions to identify unusual traffic patterns targeting DumpTS. 6. If feasible, temporarily disable or replace DumpTS with alternative tools until a secure version is released. 7. Conduct internal code reviews or fuzz testing on DumpTS if source code access is available to identify and remediate similar pointer dereference issues proactively. 8. Educate operational teams about this vulnerability and establish incident response procedures to handle potential DoS attacks effectively.
Description
A NULL Pointer Dereference discovered in DumpTS v0.1.0-nightly allows attackers to cause a denial of service via the function DumpOneStream() at /src/DumpStream.cpp.