CVE-2019-16248

low-risk
Published 2019-09-11

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

Do I need to act?

-
0.07% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.5/10 Medium
LOCAL / LOW complexity

Affected Products (1)

Affected Vendors

Telegram

References (6)

Third Party Advisory https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf
Exploit https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html
Mailing List https://www.openwall.com/lists/oss-security/2019/09/09/2
Third Party Advisory https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf
Exploit https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html
Mailing List https://www.openwall.com/lists/oss-security/2019/09/09/2
23
/ 100
low-risk
Severity 18/34 · Moderate
Exploitability 0/34 · Minimal
Exposure 5/34 · Minimal