CVE-2017-15193
moderate-risk
Published 2017-10-10
In Wireshark 2.4.0 to 2.4.1 and 2.2.0 to 2.2.9, the MBIM dissector could crash or exhaust system memory. This was addressed in epan/dissectors/packet-mbim.c by changing the memory-allocation approach.
Do I need to act?
-
0.51% 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 (12)
Affected Vendors
References (10)
Third Party Advisory
http://www.securityfocus.com/bid/101240
Issue Tracking
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14056
Vendor Advisory
https://www.wireshark.org/security/wnpa-sec-2017-43.html
Third Party Advisory
http://www.securityfocus.com/bid/101240
Issue Tracking
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14056
Vendor Advisory
https://www.wireshark.org/security/wnpa-sec-2017-43.html
45
/ 100
moderate-risk
Severity
26/34 · High
Exploitability
2/34 · Minimal
Exposure
17/34 · Moderate