Skip to main content
CVE-2024-4855VulnerabilityPublished Updated

CVE-2024-4855: Wireshark Foundation editcap · Use After Free

Affects Wireshark Foundation editcapSource CVE Database V5

0

Not known to be exploited · CVSS 3.6 Low.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 May 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
Wiresharkwireshark/editcappkg:deb/wireshark/editcapOther threatsAffected
  • =4.2.0
  • =4.0.0
  • =3.6.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-4855, organizations should: 1) Monitor Wireshark Foundation announcements and apply patches promptly once available to affected editcap versions. 2) Avoid processing capture files from untrusted or unauthenticated sources to reduce exposure to crafted malicious files. 3) Implement strict access controls to limit who can run editcap and process capture files, minimizing the risk of accidental or intentional exploitation. 4) Use sandboxing or containerization techniques to isolate editcap execution environments, preventing crashes from affecting broader systems. 5) Incorporate input validation and scanning of capture files before processing to detect anomalies or known malicious patterns. 6) Educate users about the risks of opening or processing suspicious capture files and enforce policies for secure handling of network data. 7) Consider alternative tools or updated versions with fixed vulnerabilities for critical workflows until patches are released.

Description

Use after free issue in editcap could cause denial of service via crafted capture file

References

Community reviews

Loading reviews…