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.
References
Link | Resource |
---|---|
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36 | Exploit Patch Third Party Advisory |
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/ChangeLog?h=VER-2-7 | Release Notes Third Party Advisory |
http://www.securityfocus.com/bid/97405 | Third Party Advisory VDB Entry |
https://source.android.com/security/bulletin/2017-04-01 | Third Party Advisory |
https://security.gentoo.org/glsa/201706-14 | Third Party Advisory |
http://www.securitytracker.com/id/1038201 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1038090 | Third Party Advisory VDB Entry |
http://www.debian.org/security/2017/dsa-3839 | Third Party Advisory |
https://www.oracle.com/security-alerts/cpuapr2020.html |
Information
Published : 2017-03-05 22:59
Updated : 2021-01-26 04:33
NVD link : CVE-2016-10244
Mitre link : CVE-2016-10244
JSON object : View
CWE
CWE-125
Out-of-bounds Read
Products Affected
debian
- debian_linux
freetype
- freetype