An issue was discovered in ytnef before 1.9.2. There is a potential out-of-bounds access with fields of Size 0 in TNEFParse() in libytnef.
{
"unresolved_ranges": [
{
"source": "CPE_FIELD",
"extracted_events": [
{
"last_affected": "8.0"
}
],
"cpe": "cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*"
},
{
"source": "CPE_FIELD",
"cpe": "cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*",
"extracted_events": [
{
"last_affected": "9.0"
}
]
}
]
}{
"source": "CPE_FIELD",
"cpe": "cpe:2.3:a:ytnef_project:ytnef:*:*:*:*:*:*:*:*",
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.9.1"
}
]
}