CVE-2019-16248

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).
Configurations

Configuration 1 (hide)

cpe:2.3:a:telegram:telegram:*:*:*:*:*:android:*:*

History

21 Nov 2024, 04:30

Type Values Removed Values Added
References () https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf - Third Party Advisory () https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf - Third Party Advisory
References () https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html - Exploit, Third Party Advisory () https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html - Exploit, Third Party Advisory
References () https://www.openwall.com/lists/oss-security/2019/09/09/2 - Mailing List, Third Party Advisory () https://www.openwall.com/lists/oss-security/2019/09/09/2 - Mailing List, Third Party Advisory

Information

Published : 2019-09-11 23:15

Updated : 2024-11-21 04:30


NVD link : CVE-2019-16248

Mitre link : CVE-2019-16248

CVE.ORG link : CVE-2019-16248


JSON object : View

Products Affected

telegram

  • telegram