Skip to main content
CVE-2024-9780VulnerabilityPublished Updated

CVE-2024-9780: Wireshark · Missing Initialization of a Variable

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 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-25.

What to do

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • =4.4.0
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-9780, organizations should: 1) Immediately update Wireshark to a patched version once available from the Wireshark Foundation. 2) Until a patch is released, restrict access to Wireshark to trusted users and avoid opening capture files from unverified sources. 3) Implement network segmentation to limit exposure to malicious packets targeting Wireshark instances. 4) Employ endpoint protection solutions that monitor and block abnormal application crashes or suspicious file inputs. 5) Educate users on the risks of opening untrusted capture files and enforce strict policies on file handling. 6) Use sandboxing or containerization to isolate Wireshark processes, minimizing the impact of potential crashes. 7) Monitor network traffic for anomalous packets that could exploit the ITS dissector. These targeted steps go beyond generic advice by focusing on controlling the attack vector and limiting user exposure.

Description

ITS dissector crash in Wireshark 4.4.0 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…