Skip to main content
CVE-2024-38989VulnerabilityPublished Updated

CVE-2024-38989: bunt · n/a

Affects buntSource 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
1.1% chance of exploitation in 30 days – higher than 65% 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

Affected software

ProductAffectedFixed in
GitHubizatop/buntpkg:github/izatop/buntOther threatsAffected
  • =0.29.19
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-38989, organizations should take the following specific actions: 1) Immediately audit all dependencies and software components to identify usage of izatop bunt v0.29.19 or the vulnerable /esm/qs.js module. 3) Implement runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block prototype pollution attack patterns, such as suspicious property injections in query strings or JSON payloads. 4) Conduct thorough code reviews focusing on input validation and sanitization to prevent injection of unexpected properties. 5) Employ strict Content Security Policies (CSP) and sandboxing to limit the impact of potential code execution. 6) Monitor logs and network traffic for anomalous behavior indicative of exploitation attempts. 7) Educate development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities in the future. These targeted measures go beyond generic advice by focusing on dependency management, runtime protections, and developer awareness specific to prototype pollution.

Description

izatop bunt v0.29.19 was discovered to contain a prototype pollution via the component /esm/qs.js. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…