CVE-2019-10894: High severity Wireshark Wireshark vulnerability
In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the GSS-API dissector could crash. This was addressed in epan/dissectors/packet-gssapi.c by ensuring that a valid dissector is called.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/wiresharkto a version that resolves this vulnerability.Fixed in 3.4.10-0+deb11u1Fixed in 3.4.16-0+deb11u1Fixed in 4.0.17-0+deb12u1Fixed in 4.0.11-1~deb12u1Fixed in 4.4.3-1 - Upgrade
Upgrade
alpine/wiresharkto a version that resolves this vulnerability.Fixed in 2.6.8-r0 - Compensating control
In epan/dissectors/packet-gssapi.c, ensure that a valid dissector is called.
Event History
Frequently Asked Questions
What is the severity of CVE-2019-10894?
CVE-2019-10894 has been classified as a medium severity vulnerability due to the potential for crashes in Wireshark.
How do I fix CVE-2019-10894?
To fix CVE-2019-10894, upgrade Wireshark to any of the patched versions such as 3.4.10-0+deb11u1 or later.
Which versions of Wireshark are affected by CVE-2019-10894?
CVE-2019-10894 affects Wireshark versions from 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and specifically version 3.0.0.
What component of Wireshark is impacted by CVE-2019-10894?
CVE-2019-10894 impacts the GSS-API dissector in Wireshark.
Is there a known workaround for CVE-2019-10894?
There is no known workaround for CVE-2019-10894 other than updating to a secure version of Wireshark.