CVE-2019-9208: Null Pointer Dereference
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the TCAP dissector could crash. This was addressed in epan/dissectors/asn1/tcap/tcap.cnf by avoiding NULL pointer dereferences.
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.7-r0
Event History
Frequently Asked Questions
What is the severity of CVE-2019-9208?
CVE-2019-9208 is considered a moderate severity vulnerability as it can cause a crash in Wireshark.
How do I fix CVE-2019-9208?
To fix CVE-2019-9208, upgrade Wireshark to version 2.6.7 or later.
What versions of Wireshark are affected by CVE-2019-9208?
Wireshark versions 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6 are affected by CVE-2019-9208.
Can CVE-2019-9208 be exploited remotely?
CVE-2019-9208 does not allow for remote exploitation as it involves local processing of packets.
What impact does CVE-2019-9208 have on Wireshark users?
Users of Wireshark may experience application crashes when parsing specially crafted TCAP packets due to CVE-2019-9208.