The parse_charstrings function in type1/t1load.c in FreeType 2 before 2.7 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.
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/ChangeLog?h=VER-2-7
http://www.debian.org/security/2017/dsa-3839
http://www.securityfocus.com/bid/97405
http://www.securitytracker.com/id/1038090
http://www.securitytracker.com/id/1038201
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36
https://security.gentoo.org/glsa/201706-14
Source: MITRE
Published: 2017-03-06
Updated: 2021-01-26
Type: CWE-125
Base Score: 6.8
Vector: AV:N/AC:M/Au:N/C:P/I:P/A:P
Impact Score: 6.4
Exploitability Score: 8.6
Severity: MEDIUM
Base Score: 7.8
Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Impact Score: 5.9
Exploitability Score: 1.8
Severity: HIGH