Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1444911 - (CVE-2017-7864) CVE-2017-7864 freetype: heap-based buffer overflow related to the tt_size_reset function
CVE-2017-7864 freetype: heap-based buffer overflow related to the tt_size_res...
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=20170202,repor...
: Security
Depends On: 1444915 1444916 1444917
Blocks: 1444919
  Show dependency treegraph
 
Reported: 2017-04-24 10:24 EDT by Adam Mariš
Modified: 2017-06-29 00:53 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:53:12 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:24:23 EDT
FreeType 2 before 2017-02-02 has an out-of-bounds write caused by a heap-based buffer overflow related to the tt_size_reset function in truetype/ttobjs.c.

Bug report:

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

Upstream patch:

https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=e6699596af5c5d6f0ae0ea06e19df87dce088df8
Comment 1 Adam Mariš 2017-04-24 10:29:36 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 12:29:45 EDT
This is the same case as #1444898 and #1444904. I can reliably reproduce the issue with the "regressed" commit from the original report but not with any freetype we distribute in Fedora.

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