CVE-2017-7702
moderate-risk
Published 2017-04-12
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation.
Do I need to act?
-
0.53% 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
7
CVSS 7.5/10
High
NETWORK
/ LOW complexity
Affected Products (18)
Affected Vendors
References (12)
Third Party Advisory
http://www.securityfocus.com/bid/97633
Issue Tracking
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477
Vendor Advisory
https://www.wireshark.org/security/wnpa-sec-2017-13.html
Third Party Advisory
http://www.securityfocus.com/bid/97633
Issue Tracking
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477
Vendor Advisory
https://www.wireshark.org/security/wnpa-sec-2017-13.html
47
/ 100
moderate-risk
Severity
26/34 · High
Exploitability
2/34 · Minimal
Exposure
19/34 · Moderate