CVE-2016-10244 — Out-of-bounds Read in Freetype
Severity
7.8HIGHNVD
EPSS
0.5%
top 33.42%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
Timeline
PublishedMar 6
Latest updateMay 13
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.
CVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitability: 1.8 | Impact: 5.9
Affected Packages4 packages
Also affects: Debian Linux 8.0
Patches
🔴Vulnerability Details
2📋Vendor Advisories
4Android▶
CVE-2016-10244: Android Security Bulletin 2017-04-01
CVE: CVE-2016-10244
Severity: HIGH
Affected AOSP versions: 4↗2017-04-01
Red Hat▶
freetype: parse_charstrings function in type1/t1load.c does not ensure that a font contains a glyph name↗2016-08-25
Debian▶
CVE-2016-10244: freetype - The parse_charstrings function in type1/t1load.c in FreeType 2 before 2.7 does n...↗2016
💬Community
4Bugzilla▶
CVE-2016-10244 freetype: parse_charstrings function in type1/t1load.c does not ensure that a font contains a glyph name [fedora-all]↗2017-03-07
Bugzilla▶
CVE-2016-10244 freetype: parse_charstrings function in type1/t1load.c does not ensure that a font contains a glyph name↗2017-03-07
Bugzilla▶
CVE-2016-10244 mingw-freetype: freetype: parse_charstrings function in type1/t1load.c does not ensure that a font contains a glyph name [fedora-all]↗2017-03-07
Bugzilla▶
CVE-2016-10244 mingw-freetype: freetype: parse_charstrings function in type1/t1load.c does not ensure that a font contains a glyph name [epel-7]↗2017-03-07