CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 1CVE-2021-27204
https://notcve.org/view.php?id=CVE-2021-27204
12 Feb 2021 — Telegram before 7.4 (212543) Stable on macOS stores the local passcode in cleartext, leading to information disclosure. Telegram versiones anteriores a 7.4 (212543) Stable en macOS almacena el código de acceso local en texto sin cifrar, conllevando a una la divulgación de información • https://www.inputzero.io/2020/12/telegram-privacy-fails-again.html • CWE-312: Cleartext Storage of Sensitive Information •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 1CVE-2021-27205
https://notcve.org/view.php?id=CVE-2021-27205
12 Feb 2021 — Telegram before 7.4 (212543) Stable on macOS stores the local copy of self-destructed messages in a sandbox path, leading to sensitive information disclosure. Telegram versiones anteriores a 7.4 (212543) Stable en macOS almacena la copia local de mensajes autodestruidos en una ruta de espacio aislado, conllevando a una divulgación de información confidencial • https://www.inputzero.io/2020/12/telegram-privacy-fails-again.html • CWE-312: Cleartext Storage of Sensitive Information •
CVSS: 6.5EPSS: 0%CPEs: 3EXPL: 0CVE-2020-12474
https://notcve.org/view.php?id=CVE-2020-12474
01 May 2020 — Telegram Desktop through 2.0.1, Telegram through 6.0.1 for Android, and Telegram through 6.0.1 for iOS allow an IDN Homograph attack via Punycode in a public URL or a group chat invitation URL. Telegram Desktop versiones hasta 2.0.1, Telegram versiones hasta 6.0.1 para Android y Telegram versiones hasta 6.0.1 para iOS, permiten un ataque de Homógrafo IDN por medio de un Punycode en una URL pública o una URL de invitación de chat grupal. • https://github.com/VijayT007/Vulnerability-Database/blob/master/Telegram:CVE-2020-12474 •
CVSS: 6.1EPSS: 0%CPEs: 1EXPL: 0CVE-2020-10570
https://notcve.org/view.php?id=CVE-2020-10570
24 Mar 2020 — The Telegram application through 5.12 for Android, when Show Popup is enabled, might allow physically proximate attackers to bypass intended restrictions on message reading and message replying. This might be interpreted as a bypass of the passcode feature. La aplicación Telegram versiones hasta 5.12 para Android, cuando Show Popup está habilitado, podría permitir a atacantes físicamente próximos omitir restricciones previstas en la lectura y respuesta de mensajes. Esto podría interpretarse como una omisión... • https://github.com/VijayT007/Vulnerability-Database/blob/master/Telegram:CVE-2020-10570 •
CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 1CVE-2019-16248
https://notcve.org/view.php?id=CVE-2019-16248
11 Sep 2019 — 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). La funcionalidad "delete for" en Telegram versiones anteriores a 5.11 en Android no elimina los archivos multimedia compartidos d... • https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf •
CVSS: 5.3EPSS: 5%CPEs: 2EXPL: 2CVE-2019-15514
https://notcve.org/view.php?id=CVE-2019-15514
23 Aug 2019 — The Privacy > Phone Number feature in the Telegram app 5.10 for Android and iOS provides an incorrect indication that the access level is Nobody, because attackers can find these numbers via the Group Info feature, e.g., by adding a significant fraction of a region's assigned phone numbers. openITCOCKPIT anterior de la versión 3.7.1 permite la inyección de código, La función Privacidad> Número de teléfono en la aplicación Telegram 5.10 para Android e iOS proporciona una indicación incorrecta de que el nivel... • https://github.com/bibi1959/CVE-2019-15514 •
CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 1CVE-2018-3986
https://notcve.org/view.php?id=CVE-2018-3986
03 Jan 2019 — An exploitable information disclosure vulnerability exists in the "Secret Chats" functionality of the Telegram Android messaging application version 4.9.0. The "Secret Chats" functionality allows a user to delete all traces of a chat, either by using a time trigger or by direct request. There is a bug in this functionality that leaves behind photos taken and shared on the secret chats, even after the chats are deleted. These photos will be stored in the device and accessible to all applications installed on... • http://www.securityfocus.com/bid/106295 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 2CVE-2018-20436
https://notcve.org/view.php?id=CVE-2018-20436
24 Dec 2018 — The "secret chat" feature in Telegram 4.9.1 for Android has a "side channel" in which Telegram servers send GET requests for URLs typed while composing a chat message, before that chat message is sent. There are also GET requests to other URLs on the same web server. This also affects one or more other Telegram products, such as Telegram Web-version 0.7.0. In addition, it can be interpreted as an SSRF issue. NOTE: a third party has reported that potentially unwanted behavior is caused by misconfiguration of... • https://misteralfa-hack.blogspot.com/2018/12/abusando-de-telegram-para-conseguir-una.html • CWE-918: Server-Side Request Forgery (SSRF) •
CVSS: 6.4EPSS: 0%CPEs: 1EXPL: 0CVE-2018-15542
https://notcve.org/view.php?id=CVE-2018-15542
09 Oct 2018 — An issue was discovered in the org.telegram.messenger application 4.8.11 for Android. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method's return value to true. In other words, an attacker could authenticate with an arbitrary passcode. NOTE: the vendor indicates that this is not an attack of interest within the context of their threat model, which excludes Android devices on which rooting has occurred ** EN DISPUTA ** Se ha descubierto un problema en la v... • https://gist.github.com/tanprathan/18d0f692a2485acfb5693e2f6dabeb5d • CWE-287: Improper Authentication •
CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0CVE-2018-15543
https://notcve.org/view.php?id=CVE-2018-15543
09 Oct 2018 — An issue was discovered in the org.telegram.messenger application 4.8.11 for Android. The FingerprintManager class for Biometric validation allows authentication bypass through the callback method from onAuthenticationFailed to onAuthenticationSucceeded with null, because the fingerprint API in conjunction with the Android keyGenerator class is not implemented. In other words, an attacker could authenticate with an arbitrary fingerprint. NOTE: the vendor indicates that this is not an attack of interest with... • https://gist.github.com/tanprathan/d286c0d5b02e344606287774304a1ccd • CWE-287: Improper Authentication •