Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 633992 - net-analyzer/wireshark: Multiple Denial of Service Vulnerabilities
Summary: net-analyzer/wireshark: Multiple Denial of Service Vulnerabilities
Status: RESOLVED DUPLICATE of bug 634872
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Security
URL:
Whiteboard: B3 [ebuild]
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-10 23:42 UTC by Aleksandr Wagner (Kivak)
Modified: 2017-10-20 15:58 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aleksandr Wagner (Kivak) 2017-10-10 23:42:50 UTC
CVE-2017-15193 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15193):

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. 

References:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14056
https://code.wireshark.org/review/23537
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=afb9ff7982971aba6e42472de0db4c1bedfc641b
https://www.wireshark.org/security/wnpa-sec-2017-43.html

CVE-2017-15192 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15192):

In Wireshark 2.4.0 to 2.4.1 and 2.2.0 to 2.2.9, the BT ATT dissector could crash. This was addressed in epan/dissectors/packet-btatt.c by considering a case where not all of the BTATT packets have the same encapsulation level. 

References:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14049
https://code.wireshark.org/review/23470
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=3689dc1db36037436b1616715f9a3f888fc9a0f6
https://www.wireshark.org/security/wnpa-sec-2017-42.html

CVE-2017-15191 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15191):

In Wireshark 2.4.0 to 2.4.1, 2.2.0 to 2.2.9, and 2.0.0 to 2.0.15, the DMP dissector could crash. This was addressed in epan/dissectors/packet-dmp.c by validating a string length. 

References:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14068
https://code.wireshark.org/review/23591
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=8dbb21dfde14221dab09b6b9c7719b9067c1f06e
https://www.wireshark.org/security/wnpa-sec-2017-44.html

CVE-2017-15190 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15190):

In Wireshark 2.4.0 to 2.4.1, the RTSP dissector could crash. This was addressed in epan/dissectors/packet-rtsp.c by correcting the scope of a variable. 

References:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14077
https://code.wireshark.org/review/23635
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=e27870eaa6efa1c2dac08aa41a67fe9f0839e6e0
https://www.wireshark.org/security/wnpa-sec-2017-45.html

CVE-2017-15189 (CVE-2017-15189):

In Wireshark 2.4.0 to 2.4.1, the DOCSIS dissector could go into an infinite loop. This was addressed in plugins/docsis/packet-docsis.c by adding decrements. 

References:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14080
https://code.wireshark.org/review/23663
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=625bab309d9dd21db2d8ae2aa3511810d32842a8
https://www.wireshark.org/security/wnpa-sec-2017-46.html
Comment 1 Christopher Díaz Riveros (RETIRED) gentoo-dev Security 2017-10-20 15:07:05 UTC
Thanks Kivak, 

I'm spliting it since 3 are not for us and freeing the CVE aliases.

*** This bug has been marked as a duplicate of bug 634872 ***
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2017-10-20 15:58:07 UTC
(In reply to Christopher Díaz from comment #1)
> Thanks Kivak, 
> 
> I'm spliting it since 3 are not for us and freeing the CVE aliases.
> 
> *** This bug has been marked as a duplicate of bug 634872 ***


Clippy --
     \
      Hi! Looks like you're rearranging your bug collection there. Perhaps it
      would help to put the affected versions in the Summary so you don't get
      confused so much.