Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/ChangeLog?h=VER-2-7 ↗
- http://www.securitytracker.com/id/1038090 ↗
- https://security.gentoo.org/glsa/201706-14 ↗
- https://source.android.com/security/bulletin/2017-04-01 ↗
- http://www.securityfocus.com/bid/97405 ↗
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36 ↗
- http://www.debian.org/security/2017/dsa-3839 ↗
- http://www.securitytracker.com/id/1038201 ↗
- https://www.oracle.com/security-alerts/cpuapr2020.html ↗