Bug 621951 - FreeType: Invalid read by benchmarking certain font files
Summary: FreeType: Invalid read by benchmarking certain font files
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-06 15:33 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:38 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-29 08:37:01 UTC
Embargoed:

Attachments (Terms of Use)
Local copy of PoC font file from Robert Swiecki (259.25 KB, application/x-font-ttf)
2010-08-06 15:36 UTC, Jan Lieskovsky 		no flags Details
View All

Description Jan Lieskovsky 2010-08-06 15:33:16 UTC 
An invalid read flaw was found in the way FreeType font rendering engine
performed benchmark tests on certain font files. An attacker could use this 
flaw to create a specially-crafted font file that, when opened, would cause 
an application linked against freetype to crash (denial of service).

Upstream bug report:
  [1] https://savannah.nongnu.org/bugs/?30648

Public reproducer:
  [2] http://alt.swiecki.net/j/f/sigsegv28.ttf
Comment 1 Jan Lieskovsky 2010-08-06 15:36:50 UTC 
Created attachment 437181 [details]
Local copy of PoC font file from Robert Swiecki
Comment 3 Jan Lieskovsky 2010-08-06 15:39:39 UTC 
This issue did NOT affect the versions of the freetype package, as shipped
with Red Hat Enterprise Linux 3, 4, or 5.

This issue affects the versions of the freetype package, as shipped 
with Fedora release of 12 and 13.
Comment 4 Behdad Esfahbod 2010-08-06 15:43:39 UTC 
For what it's worth, the attachment is not a TrueType file, it's a Type42 file (ie. TrueType in a PostScript container).
Comment 6 Huzaifa S. Sidhpurwala 2010-09-29 08:37:01 UTC 
This only crashes ftbench, a test application shipped with freetype.
Red Hat Security Response Team does not consider this as a security issue.
Note You need to log in before you can comment on or make changes to this bug.