First published: Tue Oct 10 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Wireshark Wireshark | =2.2.0 | |
Wireshark Wireshark | =2.2.1 | |
Wireshark Wireshark | =2.2.2 | |
Wireshark Wireshark | =2.2.3 | |
Wireshark Wireshark | =2.2.4 | |
Wireshark Wireshark | =2.2.5 | |
Wireshark Wireshark | =2.2.6 | |
Wireshark Wireshark | =2.2.7 | |
Wireshark Wireshark | =2.2.8 | |
Wireshark Wireshark | =2.2.9 | |
Wireshark Wireshark | =2.4.0 | |
Wireshark Wireshark | =2.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-15193 has a medium severity rating due to the potential for crashes or memory exhaustion.
To fix CVE-2017-15193, upgrade Wireshark to version 2.4.2 or later.
CVE-2017-15193 affects Wireshark versions 2.2.0 to 2.2.9 and 2.4.0 to 2.4.1.
CVE-2017-15193 addresses a flaw in the MBIM dissector that could lead to crashes or excessive memory use.
The Wireshark development team is responsible for addressing CVE-2017-15193 through software updates.