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.
The product reads data past the end, or before the beginning, of the intended buffer.
Link | Tags |
---|---|
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/ChangeLog?h=VER-2-7 | third party advisory release notes |
http://www.securitytracker.com/id/1038090 | vdb entry third party advisory |
https://security.gentoo.org/glsa/201706-14 | third party advisory vendor advisory |
https://source.android.com/security/bulletin/2017-04-01 | third party advisory |
http://www.securityfocus.com/bid/97405 | vdb entry third party advisory |
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36 | exploit third party advisory patch |
http://www.debian.org/security/2017/dsa-3839 | third party advisory vendor advisory |
http://www.securitytracker.com/id/1038201 | vdb entry third party advisory |
https://www.oracle.com/security-alerts/cpuapr2020.html |