Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <037768D3-D8B8-4809-913B-CCE9C2EB96E2@wolfssl.com>
Date: Thu, 17 Apr 2014 09:51:19 -0700
From: Todd A Ouska <todd@...fssl.com>
To: Raphael Geissert <geissert@...ian.org>
Cc: Open Source Security <oss-security@...ts.openwall.com>,
 cve-assign@...re.org,
 ifsecure@...il.com,
 info@...fssl.com
Subject: Re: CVE ids for CyaSSL 2.9.4?

Hi Raphael,

We've requested CVE ids for these issues.  To my knowledge they have not been assigned ids yet.  We will certainly update our advisory when they are.  Thanks for checking.

Regards,
Todd

Todd Ouska
www.wolfssl.com
todd@...fssl.com
Skype: toddouska

On Apr 17, 2014, at 5:13 AM, Raphael Geissert <geissert@...ian.org> wrote:

> Hi,
> 
> [CC'ing Ivan Fratric and one of the many @wolfssl addresses I found]
> 
> CyaSSL 2.9.4 fixes a number of security issues.
> 
> From [3]:
>> Issue #1 (Memory  Corruption)
>> Issue #2 (Out of bounds read)
>> Issue #3 (Dangerous Default Behavior, out of bounds read)
>> Issue #4 (NULL pointer dereference)
>> Issue #5 (Unknown Critical Certificate Extension Allowed)
> 
> Have CVE ids been assigned already? if not, could they be assigned?
> 
> Thanks in advance.
> 
> References:
> [0]http://www.wolfssl.com/yaSSL/Docs-cyassl-changelog.html
> [1]http://www.yassl.com/forums/topic539-cyassl-294-released.html
> [2]http://www.yassl.com/yaSSL/Blog/Entries/2014/4/9_CyaSSL_2.9.4_Released.html
> [3]http://www.yassl.com/yaSSL/Blog/Entries/2014/4/11_wolfSSL_Security_Advisory__April_9%2C_2014.html
> 
> Cheers,
> -- 
> Raphael Geissert - Debian Developer
> www.debian.org - get.debian.net
> 

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.