CVE-2017-7747: Input Validation
Published Apr 12, 2017
·Updated
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree.
Affected Software
19 affected components
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.0.8
Wireshark Wireshark=2.0.9
Wireshark Wireshark=2.0.10
Wireshark Wireshark=2.0.11
Wireshark Wireshark=2.2.0
Wireshark Wireshark=2.2.1
Wireshark Wireshark=2.2.2
Wireshark Wireshark=2.2.3
Wireshark Wireshark=2.2.4
Wireshark Wireshark=2.2.5
Debian Debian Linux=8.0
Event History
Apr 12, 2017
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Data Sourced
via NVD·11:59 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-7747?
CVE-2017-7747 has a moderate severity level due to the potential for a crash in Wireshark.
2
How do I fix CVE-2017-7747?
To fix CVE-2017-7747, upgrade Wireshark to a version later than 2.2.5 or 2.0.11.
3
Which versions of Wireshark are affected by CVE-2017-7747?
CVE-2017-7747 affects Wireshark versions 2.0.0 through 2.0.11 and 2.2.0 through 2.2.5.
4
What causes the crash in CVE-2017-7747?
The crash in CVE-2017-7747 is triggered by packet injection or a malformed capture file.
5
What mitigations are available for CVE-2017-7747?
Mitigations include avoiding the use of untrusted packet capture files and upgrading to a secure version of Wireshark.