Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1444898 - (CVE-2017-7857) CVE-2017-7857 freetype: heap-based buffer overflow related to the TT_Get_MM_Var function
CVE-2017-7857 freetype: heap-based buffer overflow related to the TT_Get_MM_V...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170308,repor...
: Security
Depends On: 1444915 1444916 1444917
Blocks: 1444919
  Show dependency treegraph
 
Reported: 2017-04-24 10:04 EDT by Adam Mariš
Modified: 2017-06-29 00:48 EDT (History)
22 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-29 00:48:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-04-24 10:04:06 EDT
FreeType 2 before 2017-03-08 has an out-of-bounds write caused by a heap-based buffer overflow related to the TT_Get_MM_Var function in truetype/ttgxvar.c and the sfnt_init_face function in sfnt/sfobjs.c.

Bug report:

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=759

Upstream patch:

https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=7bbb91fbf47fc0775cc9705673caf0c47a81f94b
Comment 1 Adam Mariš 2017-04-24 10:28:52 EDT
Created freetype tracking bugs for this issue:

Affects: fedora-all [bug 1444917]


Created mingw-freetype tracking bugs for this issue:

Affects: epel-7 [bug 1444915]
Affects: fedora-all [bug 1444916]
Comment 2 Marek Kašík 2017-04-28 11:26:40 EDT
While I can reproduce this with the commit mentioned in the chromium bug report I can not reproduce this on F24, F25, F26 or rawhide.

Note You need to log in before you can comment on or make changes to this bug.