In Wireshark 2.2.0 to 2.2.1, the Profinet I/O dissector could loop excessively, triggered by network traffic or a capture file. This was addressed in plugins/profinet/packet-pn-rtc-one.c by rejecting input with too many I/O objects.
References
Link | Resource |
---|---|
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=4127e3930ef663114567002001f44e01eba8a250 | Issue Tracking Patch |
https://www.wireshark.org/security/wnpa-sec-2016-58.html | Vendor Advisory |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12851 | Issue Tracking |
http://www.securityfocus.com/bid/94368 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1037313 |
Configurations
Configuration 1 (hide)
|
Information
Published : 2016-11-16 21:59
Updated : 2017-07-27 18:29
NVD link : CVE-2016-9372
Mitre link : CVE-2016-9372
JSON object : View
Products Affected
wireshark
- wireshark