CVE-2017-15193: High severity Wireshark Wireshark vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/wiresharkto a version that resolves this vulnerability.Fixed in 2.4.2-r0 - Upgrade
Upgrade
alpine/wiresharkto a version that resolves this vulnerability.Fixed in 2.2.10-r0
Event History
Frequently Asked Questions
What is the severity of CVE-2017-15193?
CVE-2017-15193 has a medium severity rating due to the potential for crashes or memory exhaustion.
How do I fix CVE-2017-15193?
To fix CVE-2017-15193, upgrade Wireshark to version 2.4.2 or later.
What versions of Wireshark are affected by CVE-2017-15193?
CVE-2017-15193 affects Wireshark versions 2.2.0 to 2.2.9 and 2.4.0 to 2.4.1.
What issue does CVE-2017-15193 address in Wireshark?
CVE-2017-15193 addresses a flaw in the MBIM dissector that could lead to crashes or excessive memory use.
Who is responsible for addressing CVE-2017-15193?
The Wireshark development team is responsible for addressing CVE-2017-15193 through software updates.