Learn about CVE-2019-12295 affecting Wireshark versions 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14. Find out the impact, affected systems, exploitation mechanism, and mitigation steps.
Wireshark versions 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14 were susceptible to a dissection engine crash. The issue was resolved by limiting recursion in epan/packet.c.
Understanding CVE-2019-12295
In Wireshark versions 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, a vulnerability existed that could lead to a crash in the dissection engine.
What is CVE-2019-12295?
The vulnerability in Wireshark versions allowed the dissection engine to crash due to unrestricted recursion, potentially leading to a denial of service.
The Impact of CVE-2019-12295
The vulnerability could be exploited by an attacker to cause a denial of service by crashing the dissection engine, affecting the availability of the Wireshark application.
Technical Details of CVE-2019-12295
Wireshark vulnerability details and affected systems.
Vulnerability Description
The issue in Wireshark versions was caused by the dissection engine's unrestricted recursion, leading to a crash. The problem was addressed by limiting the number of layers in epan/packet.c.
Affected Systems and Versions
Exploitation Mechanism
Attackers could exploit this vulnerability by crafting malicious network packets to trigger the dissection engine crash, causing a denial of service.
Mitigation and Prevention
Steps to mitigate and prevent the CVE-2019-12295 vulnerability.
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates