Process crash via oversized memmove in handle_chopping
Published May 14, 2024 · Updated Mar 27, 2026
Heap-buffer overflow in Editcap 3.6.0 through 3.6.22, 4.0.0 through 4.0.14, and 4.2.0 through 4.2.4 allows attackers to crash it via a malformed file. The handle_chopping function passes memmove a length that reads beyond its heap allocation while removing bytes from the start of a packet. Exploitation requires a victim to run byte chopping on the malformed capture; the demonstrated consequence is an Editcap process crash.
Summary
What happened
Heap-buffer overflow in Editcap 3.6.0 through 3.6.22, 4.0.0 through 4.0.14, and 4.2.0 through 4.2.4 allows attackers to crash it via a malformed file. The handle_chopping function passes memmove a length that reads beyond its heap allocation while removing bytes from the start of a packet. Exploitation requires a victim to run byte chopping on the malformed capture; the demonstrated consequence is an Editcap process crash.
The record
- CVE
- CVE-2024-4853
- Published
- May 14, 2024
- Updated
- Mar 27, 2026
- Vendor
- Wireshark Foundation
- Product
- Editcap
- Classifications
- CWE-762, CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.6.0 <3.6.23
- Affected versionversion=4.0.0 <4.0.15
- Affected versionversion=4.2.0 <4.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Malformed capture crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo