CVE-2016-5357: Input Validation
Published Aug 7, 2016
·Updated
wiretap/netscreen.c in the NetScreen 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
17 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
Oracle Solaris=11.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-5357?
CVE-2016-5357 has a medium severity rating as it can lead to denial of service through application crashes.
2
How do I fix CVE-2016-5357?
To fix CVE-2016-5357, upgrade to Wireshark version 1.12.12 or 2.0.4 or later.
3
What versions of Wireshark are affected by CVE-2016-5357?
Versions of Wireshark before 1.12.12 and 2.0.4, including all 1.12.x versions are affected by CVE-2016-5357.
4
Can CVE-2016-5357 be exploited remotely?
Yes, CVE-2016-5357 can be exploited remotely by providing a crafted file to execute denial of service attacks.
5
What component of Wireshark is affected by CVE-2016-5357?
CVE-2016-5357 affects the NetScreen file parser in Wireshark.