CVE-2016-5353: Input Validation
Published Aug 7, 2016
·Updated
epan/dissectors/packet-umtsfp.c in the UMTS FP dissector in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles the reserved C/T value, which allows remote attackers to cause a denial of service (application crash) via a crafted packet.
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-5353?
CVE-2016-5353 is rated as a high-severity vulnerability due to its potential for causing a denial of service attack.
2
How do I fix CVE-2016-5353?
To mitigate CVE-2016-5353, upgrade to Wireshark version 1.12.12 or 2.0.4 or later.
3
What versions of Wireshark are affected by CVE-2016-5353?
CVE-2016-5353 affects Wireshark versions 1.12.0 to 1.12.11 and 2.0.0 to 2.0.3.
4
What kind of attack is possible with CVE-2016-5353?
CVE-2016-5353 allows remote attackers to crash the Wireshark application through crafted packets.
5
Is there any workaround for CVE-2016-5353?
There are no specific workarounds for CVE-2016-5353; users should update to a patched version.