First published: Thu Nov 17 2016(Updated: )
In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Wireshark Wireshark | =2.0.0 | |
Wireshark Wireshark | =2.0.1 | |
Wireshark Wireshark | =2.0.2 | |
Wireshark Wireshark | =2.0.3 | |
Wireshark Wireshark | =2.0.4 | |
Wireshark Wireshark | =2.0.5 | |
Wireshark Wireshark | =2.0.6 | |
Wireshark Wireshark | =2.0.7 | |
Wireshark Wireshark | =2.2.0 | |
Wireshark Wireshark | =2.2.1 | |
Debian GNU/Linux | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9374 is considered a moderate severity vulnerability due to the potential for denial of service through a crash.
To fix CVE-2016-9374, update Wireshark to version 2.2.2 or later, or any version above 2.0.7.
CVE-2016-9374 affects Wireshark versions 2.0.0 to 2.0.7 and 2.2.0 to 2.2.1.
CVE-2016-9374 is classified as a buffer over-read vulnerability in the AllJoyn dissector.
CVE-2016-9374 can be triggered by malicious network traffic or specially crafted capture files.