CVE-2017-7745: High severity Wireshark Wireshark vulnerability
Published Apr 12, 2017
·Updated
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check.
Affected Software
18 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
Remediation
Patch Available
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-7745?
CVE-2017-7745 has a medium severity rating due to the potential for infinite loops leading to denial of service.
2
How do I fix CVE-2017-7745?
To fix CVE-2017-7745, update Wireshark to a version later than 2.2.5 or 2.0.11.
3
What versions of Wireshark are affected by CVE-2017-7745?
CVE-2017-7745 affects Wireshark versions from 2.0.0 to 2.0.11 and from 2.2.0 to 2.2.5.
4
What type of attack does CVE-2017-7745 involve?
CVE-2017-7745 can be triggered by packet injection or using a malformed capture file.
5
What is the impact of CVE-2017-7745 on system stability?
CVE-2017-7745 may lead to system instability by causing Wireshark to enter an infinite loop.