Description
Multiple serious vulnerabilities have been found in Wireshark. Malicious users can exploit these vulnerabilities to cause denial of service.
Below is a complete list of vulnerabilities:
- An unspecified vulnerability in LDSS dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in IEEE 1905.1a dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in RTCP dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in LTP dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in DNS dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in GSM A DTAP dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in Q.931 dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in IEEE 802.11 dissector can be exploited remotely via malformed packet trace file to cause denial of service;
- An unspecified vulnerability in RRC dissector can be exploited remotely via malformed packet trace file to cause denial of service;
Technical details
Vulnerability (2), (3) and (6) affects only Wireshark 2.6.x
Original advisories
- wnpa-sec-2018-26
- wnpa-sec-2018-30
- wnpa-sec-2018-31
- wnpa-sec-2018-27
- wnpa-sec-2018-25
- wnpa-sec-2018-32
- wnpa-sec-2018-33
- wnpa-sec-2018-29
Related products
CVE list
- CVE-2018-11354 warning
- CVE-2018-11355 warning
- CVE-2018-11356 warning
- CVE-2018-11357 warning
- CVE-2018-11358 warning
- CVE-2018-11359 warning
- CVE-2018-11360 warning
- CVE-2018-11361 warning
- CVE-2018-11362 warning
Read more
Find out the statistics of the vulnerabilities spreading in your region on statistics.securelist.com
Found an inaccuracy in the description of this vulnerability? Let us know!