First published: Thu Feb 28 2019(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/wireshark | <=2.6.5-1~deb9u1<=2.6.6-1 | |
debian/wireshark | 3.4.10-0+deb11u1 3.4.16-0+deb11u1 4.0.17-0+deb12u1 4.0.11-1~deb12u1 4.4.3-1 | |
Wireshark Wireshark | >=2.4.0<=2.4.12 | |
Wireshark Wireshark | >=2.6.0<=2.6.6 | |
Debian GNU/Linux | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-9208 is considered a moderate severity vulnerability as it can cause a crash in Wireshark.
To fix CVE-2019-9208, upgrade Wireshark to version 2.6.7 or later.
Wireshark versions 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6 are affected by CVE-2019-9208.
CVE-2019-9208 does not allow for remote exploitation as it involves local processing of packets.
Users of Wireshark may experience application crashes when parsing specially crafted TCAP packets due to CVE-2019-9208.