CVE-2017-7705: 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 RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset.
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-7705?
CVE-2017-7705 is categorized as a medium severity vulnerability.
2
How do I fix CVE-2017-7705?
To fix CVE-2017-7705, you should upgrade to Wireshark version 2.2.6 or later.
3
What versions of Wireshark are affected by CVE-2017-7705?
Versions 2.0.0 to 2.0.11 and 2.2.0 to 2.2.5 of Wireshark are affected by CVE-2017-7705.
4
What type of attack can exploit CVE-2017-7705?
CVE-2017-7705 can be exploited through packet injection or by using a malformed capture file.
5
What components of Wireshark are impacted by CVE-2017-7705?
CVE-2017-7705 impacts the RPC over RDMA dissector in Wireshark.