CVE-2016-5355: Input Validation
Published Aug 7, 2016
·Updated
wiretap/toshiba.c in the Toshiba file parser in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles sscanf unsigned-integer processing, which allows remote attackers to cause a denial of service (application crash) via a crafted file.
Affected Software
16 affected components
Wireshark Wireshark=1.12.0
Wireshark Wireshark=1.12.1
Wireshark Wireshark=1.12.2
Wireshark Wireshark=1.12.3
Wireshark Wireshark=1.12.4
Wireshark Wireshark=1.12.5
Wireshark Wireshark=1.12.6
Wireshark Wireshark=1.12.7
Wireshark Wireshark=1.12.8
Wireshark Wireshark=1.12.9
Wireshark Wireshark=1.12.10
Wireshark Wireshark=1.12.11
Wireshark Wireshark=2.0.0
Wireshark Wireshark=2.0.1
Wireshark Wireshark=2.0.2
Wireshark Wireshark=2.0.3
Event History
Aug 7, 2016
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2016-5355?
CVE-2016-5355 has been assigned a high severity level due to its potential to cause a denial of service.
2
How do I fix CVE-2016-5355?
To mitigate CVE-2016-5355, update Wireshark to version 1.12.12 or later, or 2.0.4 or later.
3
Which versions of Wireshark are affected by CVE-2016-5355?
CVE-2016-5355 affects Wireshark versions 1.12.0 through 1.12.11 and 2.0.0 through 2.0.3.
4
What type of attack does CVE-2016-5355 enable?
CVE-2016-5355 allows remote attackers to crash the application via a specially crafted file.
5
Is there a workaround for CVE-2016-5355?
There are no known workarounds for CVE-2016-5355; the best course of action is to apply the available updates.