Page 4 of 20 results (0.007 seconds)

CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 2

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 de acceso es Nadie, porque los atacantes pueden encontrar estos números a través de la función Información de grupo, por ejemplo, agregando una fracción significativa de los números de teléfono asignados de una región como RVID 1-445b21. • https://github.com/bibi1959/CVE-2019-15514 https://docs.google.com/document/d/e/2PACX-1vRx2wO2kj0axlQtv2CDSjPGlRKJOHtucvpOKGFKybh2eVVGZqvt_JJv-2Q11NHn5Y4um_F4-bgA6q5v/pub •

CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 1

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 the Android device. Existe una vulnerabilidad explotable de divulgación de información en la funcionalidad de "Chats Secretos" en la aplicación de mensajería de Telegram para Android en la versión 4.9.0. • http://www.securityfocus.com/bid/106295 https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0654 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 2

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 the "Secret chats > Preview links" setting **EN DISPUTA** La funcionalidad de "chat secreto" en la versión 4.9.1 de Telegram para Android tiene un "canal lateral" a través del cual servidores Telegram envían peticiones GET para URL tipadas mientras redactan un mensaje de chat antes de enviarlo. • https://misteralfa-hack.blogspot.com/2018/12/abusando-de-telegram-para-conseguir-una.html https://misteralfa-hack.blogspot.com/2018/12/telegram-siempre-in-middle.html • CWE-918: Server-Side Request Forgery (SSRF) •

CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0

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 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 versión 4.8.11 de la aplicación org.telegram.messenger para Android. La clase FingerprintManager para la validación biométrica permite la omisión de autenticación mediante el método callback desde onAuthenticationFailed a onAuthenticationSucceeded con un null. • https://gist.github.com/tanprathan/d286c0d5b02e344606287774304a1ccd • CWE-287: Improper Authentication •

CVSS: 6.4EPSS: 0%CPEs: 1EXPL: 0

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 versión 4.8.11 de la aplicación org.telegram.messenger para Android. La funcionalidad Passcode permite la omisión de autenticación mediante la manipulación en tiempo de ejecución que fuerza el valor de retorno de cierto método a ser "true". • https://gist.github.com/tanprathan/18d0f692a2485acfb5693e2f6dabeb5d • CWE-287: Improper Authentication •