The parse_charstrings function in type1/t1load.c in FreeType 2 does not ensure that a font contains a glyph name, which allows remote attackers to cause a denial of service (heap-based buffer over-read) or possibly have unspecified other impact via a crafted file. References: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36 Upstream patch: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/src/type1/t1load.c?h=VER-2-7&id=a660e3de422731b94d4a134d27555430cbb6fb39
Created freetype tracking bugs for this issue: Affects: fedora-all [bug 1429968] Created mingw-freetype tracking bugs for this issue: Affects: epel-7 [bug 1429969] Affects: fedora-all [bug 1429967]
Analysis: As per the patch, seems to be a OOB read, causing a crash. I dont have access to the reproducer, but seems all versions of freetype shipped with Red Hat Enterprise Linux are affected.