CVE-2017-13766: High severity wireshark vulnerability
Published Aug 30, 2017
·Updated
In Wireshark 2.4.0 and 2.2.0 to 2.2.8, the Profinet I/O dissector could crash with an out-of-bounds write. This was addressed in plugins/profinet/packet-dcerpc-pn-io.c by adding string validation.
Affected Software
24 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.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.0.12
Wireshark Wireshark=2.0.13
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.4.0
Remediation
Patch Available
Event History
Aug 30, 2017
CVE Published
via MITRE·09:00 AM
Data Sourced
via MITRE·09:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2017-13766?
CVE-2017-13766 has been assigned a high severity rating due to the potential for crashing the application.
2
How do I fix CVE-2017-13766?
To fix CVE-2017-13766, update Wireshark to version 2.6.20 or later.
3
Which versions of Wireshark are affected by CVE-2017-13766?
CVE-2017-13766 affects Wireshark versions 2.0.0 to 2.4.0.
4
What type of vulnerability is CVE-2017-13766?
CVE-2017-13766 is an out-of-bounds write vulnerability found in the Profinet I/O dissector.
5
Is there a workaround for CVE-2017-13766 before applying a patch?
There is no known workaround for CVE-2017-13766; updating to a patched version is recommended.