CVE-2016-9372
low-risk
Published 2016-11-17
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.
Do I need to act?
-
0.38% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.9/10
Medium
NETWORK
/ HIGH complexity
Affected Vendors
References (10)
Third Party Advisory
http://www.securityfocus.com/bid/94368
Issue Tracking
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12851
Vendor Advisory
https://www.wireshark.org/security/wnpa-sec-2016-58.html
Third Party Advisory
http://www.securityfocus.com/bid/94368
Issue Tracking
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12851
Vendor Advisory
https://www.wireshark.org/security/wnpa-sec-2016-58.html
26
/ 100
low-risk
Severity
18/34 · Moderate
Exploitability
1/34 · Minimal
Exposure
7/34 · Low