CVE-2024-0210: Uncontrolled Recursion in Wireshark
First published: Wed Jan 03 2024(Updated: )
Zigbee TLV dissector crash in Wireshark 4.2.0 allows denial of service via packet injection or crafted capture file
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Wireshark Wireshark | =4.2.0 |
Remedy
Upgrade to versions 4.2.0 or above.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-0210?
CVE-2024-0210 is classified as a Denial of Service vulnerability.
How do I fix CVE-2024-0210?
To fix CVE-2024-0210, upgrade Wireshark to a version later than 4.2.0.
What causes the CVE-2024-0210 vulnerability?
CVE-2024-0210 is caused by a crash in the Zigbee TLV dissector due to mishandled packet injection or crafted capture files.
Which versions of Wireshark are affected by CVE-2024-0210?
CVE-2024-0210 affects Wireshark version 4.2.0.
What can be the impact of CVE-2024-0210?
The impact of CVE-2024-0210 is a denial of service that can disrupt data packet analysis.
- agent/references
- agent/type
- agent/first-publish-date
- agent/severity
- agent/author
- agent/remedy
- agent/title
- agent/weakness
- agent/event
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/softwarecombine
- agent/description
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/tags
- agent/source
- vendor/wireshark
- canonical/wireshark wireshark
- version/wireshark wireshark/4.2.0