CVE-2017-17084: High severity Wireshark Wireshark vulnerability
Published Dec 1, 2017
·Updated
In Wireshark 2.4.0 to 2.4.2 and 2.2.0 to 2.2.10, the IWARPMPA dissector could crash. This was addressed in epan/dissectors/packet-iwarp-mpa.c by validating a ULPDU length.
Affected Software
17 affected componentsFixes available
debian/wireshark
2.6.20-0+deb10u42.6.20-0+deb10u73.4.10-0+deb11u14.0.6-1~deb12u14.0.10-1
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
Wireshark Wireshark=2.2.6
Wireshark Wireshark=2.2.7
Wireshark Wireshark=2.2.8
Wireshark Wireshark=2.2.9
Wireshark Wireshark=2.2.10
Wireshark Wireshark=2.4.0
Wireshark Wireshark=2.4.1
Wireshark Wireshark=2.4.2
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Event History
Dec 1, 2017
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2017-17084?
CVE-2017-17084 is classified as a medium severity vulnerability due to the risk of crashing Wireshark.
2
How do I fix CVE-2017-17084?
To fix CVE-2017-17084, upgrade Wireshark to version 2.4.3 or later, or apply relevant patches.
3
Which versions of Wireshark are affected by CVE-2017-17084?
CVE-2017-17084 affects Wireshark versions 2.4.0 to 2.4.2 and 2.2.0 to 2.2.10.
4
What is the impact of CVE-2017-17084 on Wireshark?
The impact of CVE-2017-17084 is that the IWARP_MPA dissector can crash Wireshark, leading to potential denial of service.
5
Who is affected by CVE-2017-17084?
Users running affected versions of Wireshark on any supported platform are at risk from CVE-2017-17084.