CVE-2024-4854
Medium · 6.4CVSS
6.4
EPSS
0.8%
Published
May 14, 2024
CISA due date
—
Cloudanix analysis
A bug in network analysis software can cause the program to freeze when it tries to read certain specially made data files, interrupting important diagnostic work.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Moderate
- Impact
- Denial Of Service
- Component
- Application
- Class
- Denial of service
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Infinite loop conditions in the MONGO and ZigBee TLV protocol dissectors cause Wireshark to hang indefinitely when processing specially crafted network packets or capture files.
Why it matters to the business
Network analysts lose access to the packet analysis tool until it is forcibly restarted, delaying troubleshooting, incident response, and security investigations that rely on Wireshark.
How an attack unfolds
An attacker creates a malicious capture file or injects crafted packets containing malformed MONGO or ZigBee TLV data; when the victim opens the file or captures the traffic in a vulnerable Wireshark version, the affected dissector enters an infinite loop and the application becomes unresponsive.
How to fix it
Upgrade to a build containing commit 4aa814ac25a18ea48d4002351ed45d4b245b0c08 or later; avoid opening untrusted capture files until updated.
How to confirm the fix worked
Confirm Wireshark reports a version built after commit 4aa814ac25a18ea48d4002351ed45d4b245b0c08; test by attempting to open a known-triggering capture file and verifying the application remains responsive.
Typical attack path
- Attacker generates a capture file or network traffic containing malformed MONGO or ZigBee TLV structures
- Victim opens the file or captures the traffic in an affected Wireshark release
- Dissector logic enters an unterminated loop
- Wireshark process consumes CPU and stops responding, requiring manual termination
How to detect it
Monitor for Wireshark processes that consume sustained high CPU without producing output or that terminate abruptly; review system logs for repeated launches of tshark or wireshark shortly after opening external capture files.
What your security team should do
- Immediately update all Wireshark installations to a build containing the referenced fix commit
- Configure Wireshark to open files in a restricted or sandboxed environment where possible
- Educate analysts to avoid loading capture files from untrusted sources until patches are applied
The record
MONGO and ZigBee TLV dissector infinite loops in Wireshark 4.2.0 to 4.2.4, 4.0.0 to 4.0.14, and 3.6.0 to 3.6.22 allow denial of service via packet injection or crafted capture file
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:11 | wireshark | 0 | 3.4.16-0+deb11u1 |
| Debian:12 | wireshark | 0 | No fix |
| Debian:13 | wireshark | 0 | 4.2.5-1 |
| Debian:14 | wireshark | 0 | 4.2.5-1 |
| Mageia:9 | wireshark | 0 | 4.0.15-1.mga9 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP5 | wireshark | 0 | 3.6.23-150000.3.115.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | wireshark | 0 | 3.6.23-150000.3.115.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | wireshark | 0 | 3.6.23-150600.18.3.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | wireshark | 0 | 3.6.23-150000.3.115.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | wireshark | 0 | 3.6.23-150600.18.3.1 |
| Ubuntu:20.04:LTS | wireshark | 0 | No fix |
| Ubuntu:22.04:LTS | wireshark | 0 | No fix |
| Ubuntu:24.04:LTS | wireshark | 0 | No fix |
| Ubuntu:24.10 | wireshark | 0 | No fix |
| Ubuntu:Pro:14.04:LTS | wireshark | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | wireshark | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | wireshark | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | wireshark | 0 | No fix |
| Ubuntu:Pro:22.04:LTS | wireshark | 0 | No fix |
| openSUSE:Leap 15.5 | wireshark | 0 | 3.6.23-150000.3.115.1 |
| openSUSE:Leap 15.6 | wireshark | 0 | 3.6.23-150600.18.3.1 |
| openSUSE:Tumbleweed | wireshark | 0 | 4.2.5-1.1 |
Related vulnerabilities
- CVE-2024-11596 ECMP dissector crash in Wireshark 4.4.0 to 4.4.1 and 4.2.0 to 4.2.8 allows denial of… Also affects wireshark
- CVE-2024-9781 AppleTalk and RELOAD Framing dissector crash in Wireshark 4.4.0 and 4.2.0 to 4.2.7 allows… Also affects wireshark
- CVE-2024-9780 ITS dissector crash in Wireshark 4.4.0 allows denial of service via packet injection or… Also affects wireshark
- CVE-2024-8645 SPRT dissector crash in Wireshark 4.2.0 to 4.0.5 and 4.0.0 to 4.0.15 allows denial of… Also affects wireshark
- CVE-2024-8250 NTLMSSP dissector crash in Wireshark 4.2.0 to 4.0.6 and 4.0.0 to 4.0.16 allows denial of… Also affects wireshark
- CVE-2024-2955 T.38 dissector crash in Wireshark 4.2.0 to 4.0.3 and 4.0.0 to 4.0.13 allows denial of… Also affects wireshark
- CVE-2023-6175 NetScreen file parser crash in Wireshark 4.0.0 to 4.0.10 and 3.6.0 to 3.6.18 allows… Also affects wireshark
- CVE-2017-17085 In Wireshark 2.4.0 to 2.4.2 and 2.2.0 to 2.2.10, the CIP Safety dissector could crash. Also affects wireshark