Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 13 Jan 2012 11:25:01 +0530
From: Huzaifa Sidhpurwala <huzaifas@...hat.com>
To: oss-security@...ts.openwall.com
CC: Kurt Seifried <kseifried@...hat.com>, Agostino Sarubbo <ago@...too.org>
Subject: Re: CVE request: Wireshark multiple vulnerabilities

On 01/12/2012 05:12 AM, Kurt Seifried wrote:
On 01/12/2012 05:12 AM, Kurt Seifried wrote:
> 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

There are 6 file format crashes here. In the interest of vendors, which 
dont always rebase to the newer version, would it be convenient to split 
these into 6 CVEs?

I doubt some older versions are affected by only some crashers.




-- 
Huzaifa Sidhpurwala / Red Hat Security Response Team

Powered by blists - more mailing lists

Your e-mail address:

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.