Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4C5C31EE.70209@redhat.com>
Date: Fri, 06 Aug 2010 18:01:50 +0200
From: Jan Lieskovsky <jlieskov@...hat.com>
To: oss-security@...ts.openwall.com
CC: "Steven M. Christey" <coley@...us.mitre.org>, Werner Lemberg <wl@....org>
Subject: Re: CVE Request -- FreeType -- Memory corruption flaw
 by processing certain LWFN fonts + three more

Hi all,

   just for more complete list. There are more of them:
     [1] https://savannah.nongnu.org/bugs/?30644
         Patch at:  http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=45a3c76b547511fa9d97aca34b150a0663257375
     [2] https://savannah.nongnu.org/bugs/?30656
         Patch at: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=c06da1ad34663da7b6fc39b030dc3ae185b96557
     [3] https://savannah.nongnu.org/bugs/?30657
         Patch at: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=346f1867fd32dae8f56e5b482d1af98f626804ac
   plus that one below (but you probably already noticed).

Thanks && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Response Team


Jan Lieskovsky wrote:
> Hi Steve, vendors,
> 
>   A memory corruption flaw was found in the way FreeType font rendering 
> engine
> processed certain Adobe Type 1 Mac Font File (LWFN) fonts. An attacker
> could use this flaw to create a specially-crafted font file that, when
> opened, would cause an application linked against libfreetype to crash,
> or, possibly execute arbitrary code.
> 
> Upstream bug report:
>   [1] https://savannah.nongnu.org/bugs/?30658
> 
> Public reproducer:
>   [2] http://alt.swiecki.net/j/f/sigsegv31.ttf
> 
> Upstream changeset:
>   [3] 
> http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=81f3472c0ba7b8f6466e2e214fa8c1c17fade975 
> 
> 
> References:
>   [4] https://bugzilla.redhat.com/show_bug.cgi?id=621907
> 
> Credit: Robert Swiecki
> 
> Could you allocate a CVE id for this?
> 
> Thanks && Regards, Jan.
> -- 
> Jan iankko Lieskovsky / 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.