Date: Wed, 11 Jan 2012 16:42:23 -0700 From: Kurt Seifried <kseifried@...hat.com> To: oss-security@...ts.openwall.com CC: Agostino Sarubbo <ago@...too.org> Subject: Re: CVE request: Wireshark multiple vulnerabilities On 01/11/2012 09:19 AM, Agostino Sarubbo wrote: > According to secunia advisory: https://secunia.com/advisories/47494/ : > > Multiple vulnerabilities have been reported in Wireshark, which can be > exploited by malicious people to cause a DoS (Denial of Service) and > compromise a user's system. > > 1) NULL pointer dereference errors when reading certain packet information can > be exploited to cause a crash. > > 2) An error within the RLC dissector can be exploited to cause a buffer > overflow via a specially crafted RLC packet capture file. > > and according with upstream advisory: > > 1)http://www.wireshark.org/security/wnpa-sec-2012-01.html > Name: Multiple Wireshark file parser vulnerabilities > Description: > Laurent Butti discovered that Wireshark failed to properly check record sizes > for many packet capture file formats. > Impact: > It may be possible to make Wireshark crash by convincing someone to read a > malformed packet trace file. Please use CVE-2012-0041 for this issue > > 2)http://www.wireshark.org/security/wnpa-sec-2012-02.html > Name: Wireshark NULL pointer vulnerabilities > Description: > Wireshark was improperly handling NULL pointers when displaying packet > information which could lead to a crash. > Impact: > It may be possible to make Wireshark crash by injecting a malformed packet > onto the wire or by convincing someone to read a malformed packet trace file. Please use CVE-2012-0042 for this issue > > 3)http://www.wireshark.org/security/wnpa-sec-2012-03.html > Name: Wireshark RLC dissector buffer overflow > Description: > The RLC dissector could overflow a buffer. > Impact: > It may be possible to make Wireshark crash by injecting a malformed packet > onto the wire or by convincing someone to read a malformed packet trace file. Please use CVE-2012-0043 for this issue -- -- Kurt Seifried / Red Hat Security Response Team
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.