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.
{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "freetype2-demos",
"binary_version": "2.5.2-1ubuntu2.6"
},
{
"binary_name": "libfreetype6",
"binary_version": "2.5.2-1ubuntu2.6"
},
{
"binary_name": "libfreetype6-dev",
"binary_version": "2.5.2-1ubuntu2.6"
}
]
}
{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "freetype2-demos",
"binary_version": "2.6.1-0.1ubuntu2.1"
},
{
"binary_name": "libfreetype6",
"binary_version": "2.6.1-0.1ubuntu2.1"
},
{
"binary_name": "libfreetype6-dev",
"binary_version": "2.6.1-0.1ubuntu2.1"
}
]
}