mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-08-04 08:44:25 +00:00
72 lines
2.5 KiB
JSON
72 lines
2.5 KiB
JSON
{
|
|
"CVE_data_meta": {
|
|
"ASSIGNER": "cve@mitre.org",
|
|
"ID": "CVE-2019-16248",
|
|
"STATE": "PUBLIC"
|
|
},
|
|
"affects": {
|
|
"vendor": {
|
|
"vendor_data": [
|
|
{
|
|
"product": {
|
|
"product_data": [
|
|
{
|
|
"product_name": "n/a",
|
|
"version": {
|
|
"version_data": [
|
|
{
|
|
"version_value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
},
|
|
"vendor_name": "n/a"
|
|
}
|
|
]
|
|
}
|
|
},
|
|
"data_format": "MITRE",
|
|
"data_type": "CVE",
|
|
"data_version": "4.0",
|
|
"description": {
|
|
"description_data": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "The \"delete for\" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient's copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient's copy of a previously sent message)."
|
|
}
|
|
]
|
|
},
|
|
"problemtype": {
|
|
"problemtype_data": [
|
|
{
|
|
"description": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references": {
|
|
"reference_data": [
|
|
{
|
|
"url": "https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html",
|
|
"refsource": "MISC",
|
|
"name": "https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html"
|
|
},
|
|
{
|
|
"url": "https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf",
|
|
"refsource": "MISC",
|
|
"name": "https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf"
|
|
},
|
|
{
|
|
"url": "https://www.openwall.com/lists/oss-security/2019/09/09/2",
|
|
"refsource": "MISC",
|
|
"name": "https://www.openwall.com/lists/oss-security/2019/09/09/2"
|
|
}
|
|
]
|
|
}
|
|
} |